DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Yigit, Ferruh" <ferruh.yigit@linux.intel.com>
To: 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>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	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: Mon, 30 Sep 2019 16:45:33 +0100	[thread overview]
Message-ID: <e160d15a-26f6-2796-fd8e-a38dee5c3077@linux.intel.com> (raw)
In-Reply-To: <20190725090345.31814-1-kirankumark@marvell.com>

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


  parent reply	other threads:[~2019-09-30 15:45 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 ` Yigit, Ferruh [this message]
2019-10-08 14:16   ` [dpdk-dev] [PATCH v3 1/3] ethdev: add NSH " Ferruh Yigit

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=e160d15a-26f6-2796-fd8e-a38dee5c3077@linux.intel.com \
    --to=ferruh.yigit@linux.intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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).