From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
To: Jerin Jacob <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
Subject: Re: [dpdk-dev] [PATCH v2] build: add support for vendor specific ARM cross builds
Date: Mon, 22 Jan 2018 20:19:31 +0530 [thread overview]
Message-ID: <20180122144930.4whmrgi6gdd4recn@Pavan-LT> (raw)
In-Reply-To: <20180122134052.GA28372@jerin>
On Mon, Jan 22, 2018 at 07:10:53PM +0530, Jerin Jacob wrote:
> -----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.
Yup missed it, now that naming and directory structure is agreed upon will
merge this patch with other set and send a v6.
>
> IMO, it will useful to update the existing meson build document for the
> cross build procedure.
>
Will update the documentation and send it as a patch in the next series.
Thanks,
Pavan.
next prev parent reply other threads:[~2018-01-22 14:50 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
2018-01-22 14:49 ` Pavan Nikhilesh [this message]
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=20180122144930.4whmrgi6gdd4recn@Pavan-LT \
--to=pbhagavatula@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=jerin.jacob@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).