patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Xueming Li <xuemingl@nvidia.com>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH 23.11 0/3] net/mlx5: rebased fixes from 24.03
Date: Wed, 1 May 2024 01:30:28 +0000	[thread overview]
Message-ID: <DM4PR12MB5373D75407FB1CAD2BD38347A1192@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240422165016.197542-1-dsosnowski@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 902 bytes --]

Hi Dariusz,

Thanks for the backporting, 3 patches applied to 23.11.1 release candidate queue.

________________________________
From: Dariusz Sosnowski <dsosnowski@nvidia.com>
Sent: Tuesday, April 23, 2024 12:50 AM
Cc: stable@dpdk.org <stable@dpdk.org>
Subject: [PATCH 23.11 0/3] net/mlx5: rebased fixes from 24.03

Rebased fixes from 24.03 release which did not apply cleanly
on 23.11 LTS branch.

Dariusz Sosnowski (2):
  net/mlx5: fix async flow create error handling
  net/mlx5: fix rollback on failed flow configure

Erez Shitrit (1):
  net/mlx5/hws: fix port ID for root table

 drivers/net/mlx5/hws/mlx5dr_matcher.c |  17 ++++
 drivers/net/mlx5/hws/mlx5dr_rule.c    |  18 ++++
 drivers/net/mlx5/mlx5_flow.h          |  22 +++++
 drivers/net/mlx5/mlx5_flow_hw.c       | 124 ++++++++++++++++++--------
 4 files changed, 142 insertions(+), 39 deletions(-)

--
2.39.2


[-- Attachment #2: Type: text/html, Size: 2430 bytes --]

      parent reply	other threads:[~2024-05-01  1:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 16:50 Dariusz Sosnowski
2024-04-22 16:50 ` [PATCH 23.11 1/3] net/mlx5/hws: fix port ID for root table Dariusz Sosnowski
2024-04-22 16:50 ` [PATCH 23.11 2/3] net/mlx5: fix async flow create error handling Dariusz Sosnowski
2024-04-22 16:50 ` [PATCH 23.11 3/3] net/mlx5: fix rollback on failed flow configure Dariusz Sosnowski
2024-05-01  1:30 ` Xueming Li [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=DM4PR12MB5373D75407FB1CAD2BD38347A1192@DM4PR12MB5373.namprd12.prod.outlook.com \
    --to=xuemingl@nvidia.com \
    --cc=dsosnowski@nvidia.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).