From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "Wang, Yipeng1" <yipeng1.wang@intel.com>,
David Marchand <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Laatz, Kevin" <kevin.laatz@intel.com>,
"aconole@redhat.com" <aconole@redhat.com>,
"nhorman@tuxdriver.com" <nhorman@tuxdriver.com>,
"Akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"anoobj@marvell.com" <anoobj@marvell.com>,
"bluca@debian.org" <bluca@debian.org>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Gobriel, Sameh" <sameh.gobriel@intel.com>,
"Van Haaren, Harry" <harry.van.haaren@intel.com>,
Luca Boccassi <luca.boccassi@gmail.com>,
"Wiles, Keith" <keith.wiles@intel.com>, nd <nd@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-stable] [PATCH v3 1/4] hash: fix meson headers packaging
Date: Thu, 30 Jan 2020 18:40:02 +0000 [thread overview]
Message-ID: <VE1PR08MB51496D98BCD75CED7CBC863098040@VE1PR08MB5149.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <D2C4A16CA39F7F4E8E384D204491D7A683145DC8@ORSMSX104.amr.corp.intel.com>
<snip>
> >Subject: [PATCH v3 1/4] hash: fix meson headers packaging
> >
> >Those headers are internal and should not be distributed.
> >
> >Fixes: 5b9656b157d3 ("lib: build with meson")
> >Cc: stable@dpdk.org
> >
> >Signed-off-by: David Marchand <david.marchand@redhat.com>
> >Acked-by: Luca Boccassi <bluca@debian.org>
>
> [Wang, Yipeng]
> Thanks for the patch! I believe they are for internal used only.
> But include Honnappa from ARM here since in the makefile seems the
> rte_crc_arm64.h is installed?
I see that this patch installs rte_crc_arm64.h. I do no see any issue.
next prev parent reply other threads:[~2020-01-30 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191220152058.10739-1-david.marchand@redhat.com>
[not found] ` <20200129172621.28565-1-david.marchand@redhat.com>
2020-01-29 17:26 ` [dpdk-stable] [PATCH v2 " David Marchand
2020-01-30 10:12 ` Luca Boccassi
2020-01-30 10:54 ` David Marchand
2020-01-30 10:56 ` [dpdk-stable] [dpdk-dev] " Luca Boccassi
[not found] ` <20200130160009.6549-1-david.marchand@redhat.com>
2020-01-30 16:00 ` [dpdk-stable] [PATCH v3 " David Marchand
2020-01-30 18:01 ` Wang, Yipeng1
2020-01-30 18:40 ` Honnappa Nagarahalli [this message]
2020-02-05 19:51 ` Wang, Yipeng1
[not found] ` <20200202210835.29791-1-david.marchand@redhat.com>
2020-02-02 21:08 ` [dpdk-stable] [PATCH v4 1/3] " David Marchand
2020-02-05 19:53 ` Wang, Yipeng1
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=VE1PR08MB51496D98BCD75CED7CBC863098040@VE1PR08MB5149.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=aconole@redhat.com \
--cc=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=keith.wiles@intel.com \
--cc=kevin.laatz@intel.com \
--cc=luca.boccassi@gmail.com \
--cc=nd@arm.com \
--cc=nhorman@tuxdriver.com \
--cc=sameh.gobriel@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yipeng1.wang@intel.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).