patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: psatheesh@marvell.com,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Kiran Kumar K <kirankumark@marvell.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	Satha Rao <skoteshwar@marvell.com>
Cc: stable@dpdk.org
Subject: Re: [PATCH 21.11] common/cnxk: fix dual VLAN parsing
Date: Mon, 20 Mar 2023 16:15:18 +0000	[thread overview]
Message-ID: <01afb69c-c987-bd0c-68c2-5ed59601462d@redhat.com> (raw)
In-Reply-To: <20230316040813.388280-1-psatheesh@marvell.com>

On 16/03/2023 04:08, psatheesh@marvell.com wrote:
> From: Satheesh Paul <psatheesh@marvell.com>
> 
> [ upstream fix 474124865694177da3d4e0a60c4686c6d5ac1e56 ]
> 
> Flow parsing was not handling pattern matching on the
> fields of inner VLAN even though MKEX profile could be
> extracting inner VLAN fields. Code has been modified
> to handle matching fields on two VLAN tags.
> 
> Fixes: c34ea71b878d ("common/cnxk: add NPC parsing API")
> 
> Signed-off-by: Satheesh Paul <psatheesh@marvell.com>
> ---
>   drivers/common/cnxk/roc_npc.h       |  19 +++
>   drivers/common/cnxk/roc_npc_parse.c | 214 +++++++++++++++++++++++-----
>   drivers/common/cnxk/roc_npc_priv.h  |   6 +
>   drivers/common/cnxk/roc_npc_utils.c |   2 +-
>   4 files changed, 206 insertions(+), 35 deletions(-)
> 

Thanks Satheesh, pushed to 21.11 branch.
Kevin.


  reply	other threads:[~2023-03-20 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16  4:08 psatheesh
2023-03-20 16:15 ` Kevin Traynor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-01  5:07 psatheesh

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=01afb69c-c987-bd0c-68c2-5ed59601462d@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=psatheesh@marvell.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.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).