From: Zhe Tao <zhe.tao@intel.com>
To: Jingjing Wu <jingjing.wu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] ethdev: fix byte order inconsistence between fdir flow and mask
Date: Wed, 2 Mar 2016 08:25:47 +0800 [thread overview]
Message-ID: <20160302002547.GA3087@intel.com> (raw)
In-Reply-To: <1454294901-2556-1-git-send-email-jingjing.wu@intel.com>
On Mon, Feb 01, 2016 at 10:48:21AM +0800, Jingjing Wu wrote:
> Fixed issue of byte order in ethdev library that the structure
> for setting fdir's mask and flow entry is inconsist and made
> inputs of mask be in big endian.
>
> Fixes: 76c6f89e80d4 ("ixgbe: support new flow director masks")
> Fixes: 2d4c1a9ea2ac ("ethdev: add new flow director masks")
>
> Reported-by: Yaacov Hazan <yaacovh@mellanox.com>
> Signed-off-by: Jingjing Wu <jingjing.wu@intel.com>
> ---
> v2 changes:
> fix typo and reword API doc.
>
> app/test-pmd/cmdline.c | 6 ++---
> doc/guides/rel_notes/release_2_3.rst | 6 +++++
> drivers/net/ixgbe/ixgbe_fdir.c | 47 ++++++++++++++++++++++--------------
> lib/librte_ether/rte_eth_ctrl.h | 17 ++++++++++---
> 4 files changed, 51 insertions(+), 25 deletions(-)
>
> diff --git a/app/test-pmd/cmdline.c b/app/test-pmd/cmdline.c
> index 73298c9..13194c9 100644
> --- a/app/test-pmd/cmdline.c
> +++ b/app/test-pmd/cmdline.c
> @@ -8687,13 +8687,13 @@ cmd_flow_director_mask_parsed(void *parsed_result,
> return;
> }
Acked-by: Zhe Tao <zhe.tao@intel.com>
next prev parent reply other threads:[~2016-03-02 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 8:37 [dpdk-dev] [PATCH] " Jingjing Wu
2016-01-27 9:19 ` Thomas Monjalon
2016-01-28 5:55 ` Wu, Jingjing
2016-02-01 2:48 ` [dpdk-dev] [PATCH v2] " Jingjing Wu
2016-03-02 0:25 ` Zhe Tao [this message]
2016-03-02 5:18 ` Lu, Wenzhuo
2016-03-04 15:52 ` Thomas Monjalon
2016-03-08 23:12 ` Thomas Monjalon
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=20160302002547.GA3087@intel.com \
--to=zhe.tao@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@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).