linux-rdma.vger.kernel.org archive mirror
 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>, Shay Drori <shayd@nvidia.com>
Subject: [PATCH net 0/3] mlx5 misc fixes 2025-09-28
Date: Mon, 29 Sep 2025 00:02:06 +0300	[thread overview]
Message-ID: <1759093329-840612-1-git-send-email-tariqt@nvidia.com> (raw)

Hi,

This patchset provides misc bug fixes from the team to the mlx5 core
driver.

Thanks,
Tariq.


Moshe Shemesh (2):
  net/mlx5: Stop polling for command response if interface goes down
  net/mlx5: fw reset, add reset timeout work

Shay Drory (1):
  net/mlx5: pagealloc: Fix reclaim race during command interface
    teardown

 drivers/net/ethernet/mellanox/mlx5/core/cmd.c |  6 ++++-
 .../ethernet/mellanox/mlx5/core/fw_reset.c    | 24 +++++++++++++++++++
 .../ethernet/mellanox/mlx5/core/pagealloc.c   |  7 ++++--
 3 files changed, 34 insertions(+), 3 deletions(-)


base-commit: 012ea489aedab1a4c08efbd936bb7be91a06d236
-- 
2.31.1


             reply	other threads:[~2025-09-28 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-28 21:02 Tariq Toukan [this message]
2025-09-28 21:02 ` [PATCH net 1/3] net/mlx5: Stop polling for command response if interface goes down Tariq Toukan
2025-09-28 21:02 ` [PATCH net 2/3] net/mlx5: pagealloc: Fix reclaim race during command interface teardown Tariq Toukan
2025-09-28 21:02 ` [PATCH net 3/3] net/mlx5: fw reset, add reset timeout work Tariq Toukan
2025-09-30  2:00 ` [PATCH net 0/3] mlx5 misc fixes 2025-09-28 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=1759093329-840612-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=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 \
    --cc=shayd@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).