public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Tariq Toukan <tariqt@nvidia.com>
To: Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
	Leon Romanovsky <leon@kernel.org>,
	Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
	<netdev@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, Gal Pressman <gal@nvidia.com>,
	Moshe Shemesh <moshe@nvidia.com>, Simon Horman <horms@kernel.org>
Subject: [PATCH net V2 0/4] mlx5 misc fixes 2026-01-27
Date: Tue, 27 Jan 2026 10:52:37 +0200	[thread overview]
Message-ID: <1769503961-124173-1-git-send-email-tariqt@nvidia.com> (raw)

Hi,

This patchset provides misc bug fixes from the team to the mlx5 core and
Eth drivers.

Thanks,
Tariq.

V2:
- Fix issue in patch #4 (AI-generated review).
- Add review tags (Simon).
- Link to V1: https://lore.kernel.org/all/20260120081654.1639138-1-tariqt@nvidia.com/


Cosmin Ratiu (1):
  net/mlx5: Fix deadlock between devlink lock and esw->wq

Jianbo Liu (1):
  net/mlx5e: Skip ESN replay window setup for IPsec crypto offload

Parav Pandit (1):
  net/mlx5: Fix vhca_id access call trace use before alloc

Shay Drory (1):
  net/mlx5: fs, Fix inverted cap check in tx flow table root disconnect

 .../net/ethernet/mellanox/mlx5/core/debugfs.c    | 16 ++++++++++++++++
 .../ethernet/mellanox/mlx5/core/en_accel/ipsec.c |  3 ++-
 .../net/ethernet/mellanox/mlx5/core/eswitch.c    |  6 +++++-
 .../net/ethernet/mellanox/mlx5/core/eswitch.h    |  1 +
 .../mellanox/mlx5/core/eswitch_offloads.c        | 12 +++++++++++-
 drivers/net/ethernet/mellanox/mlx5/core/fs_cmd.c |  3 ++-
 drivers/net/ethernet/mellanox/mlx5/core/main.c   | 14 +++-----------
 .../net/ethernet/mellanox/mlx5/core/mlx5_core.h  |  1 +
 .../ethernet/mellanox/mlx5/core/sf/dev/driver.c  |  1 +
 9 files changed, 42 insertions(+), 15 deletions(-)


base-commit: 165c34fb6068ff153e3fc99a932a80a9d5755709
-- 
2.40.1


             reply	other threads:[~2026-01-27  8:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27  8:52 Tariq Toukan [this message]
2026-01-27  8:52 ` [PATCH net V2 1/4] net/mlx5: fs, Fix inverted cap check in tx flow table root disconnect Tariq Toukan
2026-01-27  8:52 ` [PATCH net V2 2/4] net/mlx5: Fix deadlock between devlink lock and esw->wq Tariq Toukan
2026-01-29  4:56   ` Jakub Kicinski
2026-01-29 10:33     ` Cosmin Ratiu
2026-01-29 23:40       ` Jakub Kicinski
2026-02-02 14:48         ` Cosmin Ratiu
2026-02-03  0:29           ` Jakub Kicinski
2026-01-27  8:52 ` [PATCH net V2 3/4] net/mlx5: Fix vhca_id access call trace use before alloc Tariq Toukan
2026-01-27  8:52 ` [PATCH net V2 4/4] net/mlx5e: Skip ESN replay window setup for IPsec crypto offload Tariq Toukan
2026-01-29  5:00 ` [PATCH net V2 0/4] mlx5 misc fixes 2026-01-27 patchwork-bot+netdevbpf

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=1769503961-124173-1-git-send-email-tariqt@nvidia.com \
    --to=tariqt@nvidia.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=moshe@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@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