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>,
"Richard Cochran" <richardcochran@gmail.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>,
Dragos Tatulea <dtatulea@nvidia.com>
Subject: [PATCH net-next 0/5] net/mlx5: misc changes 2025-11-17
Date: Mon, 17 Nov 2025 23:42:04 +0200 [thread overview]
Message-ID: <1763415729-1238421-1-git-send-email-tariqt@nvidia.com> (raw)
Hi,
This series contains misc enhancements to the mlx5 driver.
Regards,
Tariq
Carolina Jubran (2):
net/mlx5e: Recover SQ on excessive PTP TX timestamp delta
net/mlx5: Remove redundant bw_share minimal value assignment
Gal Pressman (1):
net/mlx5: Refactor EEPROM query error handling to return status
separately
Saeed Mahameed (1):
net/mlx5: Abort new commands if all command slots are stalled
Tariq Toukan (1):
net/mlx5: Use EOPNOTSUPP instead of ENOTSUPP
drivers/net/ethernet/mellanox/mlx5/core/cmd.c | 55 +++++++++++++++++++
.../mellanox/mlx5/core/diag/fw_tracer.c | 2 +-
.../net/ethernet/mellanox/mlx5/core/en/ptp.c | 21 +++++--
.../net/ethernet/mellanox/mlx5/core/en/ptp.h | 2 +-
.../ethernet/mellanox/mlx5/core/en_ethtool.c | 19 ++++---
.../mellanox/mlx5/core/en_fs_ethtool.c | 2 +-
.../net/ethernet/mellanox/mlx5/core/en_tx.c | 2 +-
.../net/ethernet/mellanox/mlx5/core/esw/qos.c | 7 ---
.../ethernet/mellanox/mlx5/core/fpga/core.c | 2 +-
.../ethernet/mellanox/mlx5/core/lib/vxlan.c | 2 +-
.../ethernet/mellanox/mlx5/core/mlx5_core.h | 4 +-
.../net/ethernet/mellanox/mlx5/core/port.c | 35 ++++++------
.../mlx5/core/steering/sws/dr_domain.c | 8 +--
include/linux/mlx5/driver.h | 1 +
14 files changed, 111 insertions(+), 51 deletions(-)
base-commit: c9dfb92de0738eb7fe6a591ad1642333793e8b6e
--
2.31.1
next reply other threads:[~2025-11-17 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 21:42 Tariq Toukan [this message]
2025-11-17 21:42 ` [PATCH net-next 1/5] net/mlx5: Refactor EEPROM query error handling to return status separately Tariq Toukan
2025-11-19 23:11 ` Matthew W Carlis
2025-11-23 7:11 ` Gal Pressman
2025-11-17 21:42 ` [PATCH net-next 2/5] net/mlx5e: Recover SQ on excessive PTP TX timestamp delta Tariq Toukan
2025-11-17 21:42 ` [PATCH net-next 3/5] net/mlx5: Remove redundant bw_share minimal value assignment Tariq Toukan
2025-11-17 21:42 ` [PATCH net-next 4/5] net/mlx5: Abort new commands if all command slots are stalled Tariq Toukan
2025-11-17 21:42 ` [PATCH net-next 5/5] net/mlx5: Use EOPNOTSUPP instead of ENOTSUPP Tariq Toukan
2025-11-19 3:20 ` [PATCH net-next 0/5] net/mlx5: misc changes 2025-11-17 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=1763415729-1238421-1-git-send-email-tariqt@nvidia.com \
--to=tariqt@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--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=richardcochran@gmail.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
all inboxes | Powered by JetHome®