patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Alvin Zhang <alvinx.zhang@intel.com>, <beilei.xing@intel.com>,
	<junfeng.guo@intel.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>, Qi Zhang <qi.z.zhang@intel.com>
Subject: Re: [dpdk-stable] [PATCH] net/i40e: fix IPv6 fragment RSS offload type in flow
Date: Fri, 15 Oct 2021 21:50:27 +0100	[thread overview]
Message-ID: <1aa05e3f-a85e-f1d8-d39a-ab9fb8ecc98e@intel.com> (raw)
In-Reply-To: <20211012083932.1428-1-alvinx.zhang@intel.com>

On 10/12/2021 9:39 AM, Alvin Zhang wrote:
> To keep flow format uniform with ice, this patch adds support for
> this RSS rule:
>      flow create 0 ingress pattern eth / ipv6_frag_ext / end actions \
>      rss types ipv6-frag end queues end queues end / end
> 
> Fixes: ef4c16fd9148 ("net/i40e: refactor RSS flow")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Alvin Zhang <alvinx.zhang@intel.com>

'./devtools/check-doc-vs-code.sh' script is failing [1], can you please
fix it?

[1]
$ ./devtools/check-doc-vs-code.sh
rte_flow doc out of sync for i40e
         item ipv6_frag_ext


  parent reply	other threads:[~2021-10-15 20:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12  8:39 Alvin Zhang
2021-10-15  9:36 ` [dpdk-stable] [dpdk-dev] " Jiang, YuX
2021-10-15 13:45   ` Zhang, Qi Z
2021-10-15 20:50 ` Ferruh Yigit [this message]
2021-10-19  0:03   ` [dpdk-stable] " Zhang, Qi Z
2021-10-19  1:31     ` Zhang, AlvinX
2021-10-19  1:51       ` Zhang, Qi Z
2021-10-19  1:53 ` [dpdk-stable] [PATCH v2] " Alvin Zhang
2021-10-19 11:05   ` Zhang, Qi Z

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=1aa05e3f-a85e-f1d8-d39a-ab9fb8ecc98e@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=alvinx.zhang@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=junfeng.guo@intel.com \
    --cc=qi.z.zhang@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).