From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
"Laatz, Kevin" <kevin.laatz@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"jianbo.liu@arm.com" <jianbo.liu@arm.com>,
"gavin.hu@arm.com" <gavin.hu@arm.com>
Subject: Re: [dpdk-dev] [PATCH v3 1/3] lib/librte_table: add hash_func header files
Date: Tue, 25 Sep 2018 09:15:00 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891268E7B0FCF@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <20180925044228.GA21250@jerin>
> ARM specific change and this patchset looks good. But, It has following
> checkpatches.sh and check-git-log.sh errors.
>
Thanks, Jerin, this looks like a map file issue, we'll work to fix it.
Regards,
Cristian
next prev parent reply other threads:[~2018-09-25 9:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 10:06 Kevin Laatz
2018-09-07 10:06 ` [dpdk-dev] [PATCH v3 2/3] examples/ip_pipeline: modify application to use librte_table headers Kevin Laatz
2018-09-07 10:20 ` Gavin Hu (Arm Technology China)
2018-09-07 10:06 ` [dpdk-dev] [PATCH v3 3/3] net/softnic: modify softnic " Kevin Laatz
2018-09-07 10:20 ` Gavin Hu (Arm Technology China)
2018-09-25 4:42 ` [dpdk-dev] [PATCH v3 1/3] lib/librte_table: add hash_func header files Jerin Jacob
2018-09-25 9:15 ` Dumitrescu, Cristian [this message]
2018-09-25 15:32 ` [dpdk-dev] [PATCH v4 1/3] lib/librte_table: add hash func " Kevin Laatz
2018-09-25 15:32 ` [dpdk-dev] [PATCH v4 2/3] examples/ip_pipeline: modify to use new table lib headers Kevin Laatz
2018-09-25 16:27 ` Jerin Jacob
2018-09-25 15:32 ` [dpdk-dev] [PATCH v4 3/3] net/softnic: " Kevin Laatz
2018-09-25 16:28 ` Jerin Jacob
2018-09-25 16:25 ` [dpdk-dev] [PATCH v4 1/3] lib/librte_table: add hash func header files Jerin Jacob
2018-09-28 10:34 ` Dumitrescu, Cristian
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=3EB4FA525960D640B5BDFFD6A3D891268E7B0FCF@IRSMSX107.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jianbo.liu@arm.com \
--cc=kevin.laatz@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).