patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>, "Zhao1, Wei" <wei.zhao1@intel.com>
Subject: Re: [dpdk-stable] [PATCH v3 13/14] ethdev: fix incomplete items in flow API
Date: Thu, 27 Apr 2017 01:03:55 +0000	[thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B59D014@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <fbf626e53d691fa787ac5bdbf1b530553e24b10f.1493208189.git.adrien.mazarguil@6wind.com>

Hi,

> -----Original Message-----
> From: Adrien Mazarguil [mailto:adrien.mazarguil@6wind.com]
> Sent: Wednesday, April 26, 2017 8:07 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Zhao1, Wei; Lu, Wenzhuo
> Subject: [PATCH v3 13/14] ethdev: fix incomplete items in flow API
> 
> E-Tag and NVGRE pattern items have been added hastily without updating
> documentation nor testpmd.
> 
> This commit also adds default masks for these items based on the ixgbe
> implementation.
> 
> Fixes: 99e7003831c3 ("net/ixgbe: parse L2 tunnel filter")
> 
> Cc: stable@dpdk.org
> Cc: Wei Zhao <wei.zhao1@intel.com>
> Cc: Wenzhuo Lu <wenzhuo.lu@intel.com>
> Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
Thanks for this patch :)

  reply	other threads:[~2017-04-27  1:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1493048352.git.adrien.mazarguil@6wind.com>
2017-04-24 15:53 ` [dpdk-stable] [PATCH 06/13] mbuf: fix missing includes in exported header Adrien Mazarguil
2017-04-24 15:53 ` [dpdk-stable] [PATCH 09/13] efd: fix missing include " Adrien Mazarguil
2017-04-24 15:53 ` [dpdk-stable] [PATCH 11/13] ethdev: fix C++ errors in flow API Adrien Mazarguil
2017-04-24 15:53 ` [dpdk-stable] [PATCH 13/13] ethdev: fix incomplete items " Adrien Mazarguil
     [not found] ` <cover.1493108423.git.adrien.mazarguil@6wind.com>
2017-04-25  8:30   ` [dpdk-stable] [PATCH v2 06/13] mbuf: fix missing includes in exported header Adrien Mazarguil
2017-04-25  9:56     ` Olivier Matz
2017-04-25  8:30   ` [dpdk-stable] [PATCH v2 09/13] efd: fix missing include " Adrien Mazarguil
2017-04-25  8:30   ` [dpdk-stable] [PATCH v2 11/13] ethdev: fix C++ errors in flow API Adrien Mazarguil
2017-04-25 11:35     ` Shahaf Shuler
2017-04-25  8:30   ` [dpdk-stable] [PATCH v2 13/13] ethdev: fix incomplete items " Adrien Mazarguil
     [not found]   ` <cover.1493208189.git.adrien.mazarguil@6wind.com>
2017-04-26 12:07     ` [dpdk-stable] [PATCH v3 06/14] mbuf: fix missing includes in exported header Adrien Mazarguil
2017-04-26 12:07     ` [dpdk-stable] [PATCH v3 09/14] efd: fix missing include " Adrien Mazarguil
2017-04-26 15:36       ` De Lara Guarch, Pablo
2017-04-26 12:07     ` [dpdk-stable] [PATCH v3 11/14] ethdev: fix C++ errors in flow API Adrien Mazarguil
2017-04-26 12:07     ` [dpdk-stable] [PATCH v3 13/14] ethdev: fix incomplete items " Adrien Mazarguil
2017-04-27  1:03       ` Lu, Wenzhuo [this message]
2017-04-26 12:07     ` [dpdk-stable] [PATCH v3 14/14] eal: fix debug macro redefinition Adrien Mazarguil

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=6A0DE07E22DDAD4C9103DF62FEBC09093B59D014@shsmsx102.ccr.corp.intel.com \
    --to=wenzhuo.lu@intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=wei.zhao1@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).