DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Rongwei Liu <rongweil@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>,
	Matan Azrad <matan@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Ori Kam <orika@nvidia.com>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Subject: RE: [PATCH v1 0/2] disallow duplicated tag index
Date: Wed, 24 May 2023 14:05:29 +0000	[thread overview]
Message-ID: <MN2PR12MB30868D4565215851235954C2CF419@MN2PR12MB3086.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230516054329.1397016-1-rongweil@nvidia.com>

Hi,

> -----Original Message-----
> From: Rongwei Liu <rongweil@nvidia.com>
> Sent: Tuesday, May 16, 2023 8:43 AM
> To: dev@dpdk.org; Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; NBU-Contact-
> Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>
> Subject: [PATCH v1 0/2] disallow duplicated tag index
> 
> Doesn't allow duplicated tag index matching.
> 
> Rongwei Liu (2):
>   net/mlx5: disallow duplicated tag index in pattern template
>   net/mlx5: fix sws duplicated tag index matching
> 
>  drivers/net/mlx5/mlx5_flow_dv.c | 21 +++++++++++++++++++--
> drivers/net/mlx5/mlx5_flow_hw.c | 25 +++++++++++++++++++++----
>  2 files changed, 40 insertions(+), 6 deletions(-)
> 
> --
> 2.27.0

Series applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      parent reply	other threads:[~2023-05-24 14:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16  5:43 Rongwei Liu
2023-05-16  5:43 ` [PATCH v1 1/2] net/mlx5: disallow duplicated tag index in pattern template Rongwei Liu
2023-05-17 17:11   ` Ori Kam
2023-05-16  5:43 ` [PATCH v1 2/2] net/mlx5: fix sws duplicated tag index matching Rongwei Liu
2023-05-24 14:05 ` Raslan Darawsheh [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=MN2PR12MB30868D4565215851235954C2CF419@MN2PR12MB3086.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rongweil@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.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).