From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Wu, Jingjing" <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: Fri, 04 Mar 2016 16:52:23 +0100 [thread overview]
Message-ID: <2991278.2Zunq92sYN@xps13> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC090903436EE3@shsmsx102.ccr.corp.intel.com>
> > 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>
> Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
Applied, thanks
next prev parent reply other threads:[~2016-03-04 15:54 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
2016-03-02 5:18 ` Lu, Wenzhuo
2016-03-04 15:52 ` Thomas Monjalon [this message]
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=2991278.2Zunq92sYN@xps13 \
--to=thomas.monjalon@6wind.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).