From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@linux.intel.com>,
kirankumark@marvell.com,
Adrien Mazarguil <adrien.mazarguil@6wind.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Andrew Rybchenko <arybchenko@solarflare.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 1/3] ethdev: add NSH key field to flow API
Date: Tue, 8 Oct 2019 15:16:16 +0100 [thread overview]
Message-ID: <7118f741-cd67-7efc-7753-90eb77bc992f@intel.com> (raw)
In-Reply-To: <e160d15a-26f6-2796-fd8e-a38dee5c3077@linux.intel.com>
On 9/30/2019 4:45 PM, Yigit, Ferruh wrote:
> On 7/25/2019 10:03 AM, kirankumark@marvell.com wrote:
>> From: Kiran Kumar K <kirankumark@marvell.com>
>>
>> Add new rte_flow_item_nsh in order to match the network service header
>> based on RFC 8300.
>>
>> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
>
> Hi Adrien, Ori,
>
> Any concern/objection on the patchset [1], if not will be merged in next a few days.
>
> Thanks,
> ferruh
>
> [1]
> https://patches.dpdk.org/user/todo/dpdk/?series=5739
> ethdev: add NSH key field to flow API
> ethdev: add IGMP key field to flow API
> ethdev: add AH key field to flow API
>
For series,
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-10-08 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 9:03 kirankumark
2019-07-25 9:03 ` [dpdk-dev] [PATCH v3 2/3] ethdev: add IGMP " kirankumark
2019-07-25 9:03 ` [dpdk-dev] [PATCH v3 3/3] ethdev: add AH " kirankumark
2019-09-30 15:45 ` [dpdk-dev] [PATCH v3 1/3] ethdev: add NSH " Yigit, Ferruh
2019-10-08 14:16 ` Ferruh Yigit [this message]
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=7118f741-cd67-7efc-7753-90eb77bc992f@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@linux.intel.com \
--cc=john.mcnamara@intel.com \
--cc=kirankumark@marvell.com \
--cc=marko.kovacevic@intel.com \
--cc=thomas@monjalon.net \
/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).