From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: bruce.richardson@intel.com, harry.van.haaren@intel.com,
herbert.guan@arm.com, hemant.agrawal@nxp.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] build: add support for vendor specific ARM cross builds
Date: Mon, 22 Jan 2018 19:10:53 +0530 [thread overview]
Message-ID: <20180122134052.GA28372@jerin> (raw)
In-Reply-To: <20180122131450.8855-1-pbhagavatula@caviumnetworks.com>
-----Original Message-----
> Date: Mon, 22 Jan 2018 18:44:50 +0530
> From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> To: jerin.jacob@caviumnetworks.com, bruce.richardson@intel.com,
> harry.van.haaren@intel.com, herbert.guan@arm.com, hemant.agrawal@nxp.com
> Cc: dev@dpdk.org, Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> Subject: [dpdk-dev] [PATCH v2] build: add support for vendor specific ARM
> cross builds
> X-Mailer: git-send-email 2.14.1
>
> Add various vendor specific cross build targets.
> This can be verified by using linaro toolchain and running
>
> meson build --cross-file config/arm/arch64_armv8_<cpu>_cross
Looks like git comment is _not_ updated. i.e comment is not sync with filename.
IMO, it will useful to update the existing meson build document for the
cross build procedure.
next prev parent reply other threads:[~2018-01-22 13:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 13:15 [dpdk-dev] [PATCH] " Pavan Nikhilesh
2018-01-19 16:41 ` Bruce Richardson
2018-01-19 17:26 ` Pavan Nikhilesh
2018-01-19 17:35 ` Bruce Richardson
2018-01-22 12:38 ` Jerin Jacob
2018-01-22 13:14 ` [dpdk-dev] [PATCH v2] " Pavan Nikhilesh
2018-01-22 13:40 ` Jerin Jacob [this message]
2018-01-22 14:49 ` Pavan Nikhilesh
2018-01-22 14:12 ` Bruce Richardson
2018-01-22 14:26 ` Pavan Nikhilesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180122134052.GA28372@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=herbert.guan@arm.com \
--cc=pbhagavatula@caviumnetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).