From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Wei Zhao <wei.zhao1@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/ixgbe: fix parsing fdir vxlan issue
Date: Tue, 14 Feb 2017 15:32:27 +0800 [thread overview]
Message-ID: <20170214073227.GU20916@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <d644a67f-39f9-080e-e14d-885078dbf60b@intel.com>
On Fri, Feb 03, 2017 at 10:53:29PM +0000, Ferruh Yigit wrote:
> On 2/3/2017 8:44 AM, Wei Zhao wrote:
> > VNI of VXLAN is parsed wrongly. The root cause is that
> > array vni in item VXLAN also uses network byte ordering.
> >
> > Fixes: 11777435c727 ("net/ixgbe: parse flow director filter")
> >
> > Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
>
> Cc: stable@dpdk.org
It fixed an issue introduced in this release, thus it's not a candidate
for a stable release. Dropped.
--yliu
>
> Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2017-02-14 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 8:44 Wei Zhao
2017-02-03 22:53 ` Ferruh Yigit
2017-02-14 7:32 ` Yuanhan Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-03 8:41 Wei Zhao
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=20170214073227.GU20916@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).