patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Steve Yang <stevex.yang@intel.com>, stable@dpdk.org
Cc: beilei.xing@intel.com, jia.guo@intel.com,
	Guinan Sun <guinanx.sun@intel.com>
Subject: Re: [dpdk-stable] [DPDK 18.11] net/i40e: fix recreating flexible flow director rule
Date: Fri, 11 Dec 2020 09:47:11 +0000	[thread overview]
Message-ID: <849b67fe-4c74-ea67-171b-1b27912bcc4a@redhat.com> (raw)
In-Reply-To: <20201211090105.28432-5-stevex.yang@intel.com>

On 11/12/2020 09:01, Steve Yang wrote:
> From: Guinan Sun <guinanx.sun@intel.com>
> 
> [ upstream commit 0acf70d473072fd77b667a0419f8b9ab70b35b39 ]
> 
> This patch fixes the failure of recreate flexible fdir rule.
> The root cause is that the flex_mask_flag is not reset during
> flow destroy and flow flush.
> 
> Fixes: 6ced3dd72f5f ("net/i40e: support flexible payload parsing for FDIR")
> Cc: stable@dpdk.org
> 
> Acked-by: Qi Zhang <qi.z.zhang@intel.com>
> 
> Signed-off-by: Guinan Sun <guinanx.sun@intel.com>
> ---
>  drivers/net/i40e/i40e_fdir.c | 6 ++++++
>  drivers/net/i40e/i40e_flow.c | 4 +++-
>  2 files changed, 9 insertions(+), 1 deletion(-)

Applied, thanks.


  reply	other threads:[~2020-12-11  9:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11  9:01 [dpdk-stable] [DPDK 18.11] net/i40e: fix filter pctype Steve Yang
2020-12-11  9:01 ` [dpdk-stable] [DPDK 18.11] net/i40e: fix flow director initialisation Steve Yang
2020-12-11  9:46   ` Kevin Traynor
2020-12-11  9:01 ` [dpdk-stable] [DPDK 18.11] net/i40e: fix link status Steve Yang
2020-12-11  9:46   ` Kevin Traynor
2020-12-11  9:01 ` [dpdk-stable] [DPDK 18.11] net/i40e: fix queue region in RSS flow Steve Yang
2020-12-11  9:44   ` Kevin Traynor
2020-12-11  9:01 ` [dpdk-stable] [DPDK 18.11] net/i40e: fix recreating flexible flow director rule Steve Yang
2020-12-11  9:47   ` Kevin Traynor [this message]
2020-12-11  9:46 ` [dpdk-stable] [DPDK 18.11] net/i40e: fix filter pctype Kevin Traynor

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=849b67fe-4c74-ea67-171b-1b27912bcc4a@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=beilei.xing@intel.com \
    --cc=guinanx.sun@intel.com \
    --cc=jia.guo@intel.com \
    --cc=stable@dpdk.org \
    --cc=stevex.yang@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).