DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Bing Zhao <bingz@nvidia.com>,
	Dariusz Sosnowski <dsosnowski@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>,
	Matan Azrad <matan@nvidia.com>
Subject: Re: [PATCH 0/4] non-template fixes set
Date: Thu, 29 Aug 2024 08:59:18 +0000	[thread overview]
Message-ID: <CH3PR12MB8460657554E3F6B833F65BAACF962@CH3PR12MB8460.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240723081522.1087433-1-bingz@nvidia.com>

Hi,

From: Bing Zhao <bingz@nvidia.com>
Sent: Tuesday, July 23, 2024 11:15 AM
To: Dariusz Sosnowski; Slava Ovsiienko; dev@dpdk.org; Raslan Darawsheh
Cc: Ori Kam; Suanming Mou; Matan Azrad
Subject: [PATCH 0/4] non-template fixes set

A set for cumulative fixes of non-template API support.

Bing Zhao (4):
  net/mlx5/hws: fix state detection of queue full in polling
  net/mlx5: fix releasing order of compatible matcher
  net/mlx5: fix matcher mask translation
  net/mlx5: fix log error on non-template rule destroy

 drivers/net/mlx5/hws/mlx5dr_bwc.c |  4 +++-
 drivers/net/mlx5/hws/mlx5dr_bwc.h |  1 -
 drivers/net/mlx5/mlx5_flow_dv.c   |  1 +
 drivers/net/mlx5/mlx5_flow_hw.c   | 37 +++++++++++--------------------
 4 files changed, 17 insertions(+), 26 deletions(-)

Series applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh


      parent reply	other threads:[~2024-08-29  8:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23  8:15 Bing Zhao
2024-07-23  8:15 ` [PATCH 1/4] net/mlx5/hws: fix state detection of queue full in polling Bing Zhao
2024-07-23  8:15 ` [PATCH 2/4] net/mlx5: fix releasing order of compatible matcher Bing Zhao
2024-07-23  8:15 ` [PATCH 3/4] net/mlx5: fix matcher mask translation Bing Zhao
2024-07-23  8:15 ` [PATCH 4/4] net/mlx5: fix log error on non-template rule destroy Bing Zhao
2024-08-29  8:59 ` 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=CH3PR12MB8460657554E3F6B833F65BAACF962@CH3PR12MB8460.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=suanmingm@nvidia.com \
    --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).