From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Beilei Xing <beilei.xing@intel.com>, jingjing.wu@intel.com
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] net/i40e: fix flow director for IPv6
Date: Fri, 23 Jun 2017 10:07:39 +0100 [thread overview]
Message-ID: <fa722152-9105-6400-b535-dabce59120f5@intel.com> (raw)
In-Reply-To: <1498123852-91591-1-git-send-email-beilei.xing@intel.com>
On 6/22/2017 10:30 AM, Beilei Xing wrote:
> After adding a fdir rule for IPv6 with input set TC, IPv6 packets
> with the specific TC can't be assigned the right queue.
> The root cause is that TC is parsed wrongly, this patch fixes
> TC parsing problem.
>
> Fixes: 7d83c152a207 ("net/i40e: parse flow director filter")
> Cc: stable@dpdk.org
>
> Signed-off-by: Beilei Xing <beilei.xing@intel.com>
Tested-by: Yuan Peng <yuan.peng@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-06-23 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 9:30 Beilei Xing
2017-06-23 3:04 ` [dpdk-stable] [dpdk-dev] " Peng, Yuan
2017-06-23 9:07 ` Ferruh Yigit [this message]
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=fa722152-9105-6400-b535-dabce59120f5@intel.com \
--to=ferruh.yigit@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=stable@dpdk.org \
/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).