From: Tariq Toukan <tariqt@nvidia.com>
To: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, <netdev@vger.kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Cc: Akiva Goldberger <agoldberger@nvidia.com>,
Alex Vesker <valex@nvidia.com>, Cosmin Ratiu <cratiu@nvidia.com>,
Dragos Tatulea <dtatulea@nvidia.com>,
"Erez Shitrit" <erezsh@nvidia.com>, Gal Pressman <gal@nvidia.com>,
Jacob Keller <jacob.e.keller@intel.com>,
Kees Cook <kees@kernel.org>, Leon Romanovsky <leon@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
Mark Bloch <mbloch@nvidia.com>, Moshe Shemesh <moshe@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>, Shay Drory <shayd@nvidia.com>,
Simon Horman <horms@kernel.org>, Tariq Toukan <tariqt@nvidia.com>,
Vlad Dogaru <vdogaru@nvidia.com>,
Yevgeny Kliteynik <kliteyn@nvidia.com>
Subject: [PATCH net-next V3 0/5] net/mlx5: HWS misc enhancements
Date: Sun, 16 Aug 2026 17:20:40 +0300 [thread overview]
Message-ID: <20260816142045.3289452-1-tariqt@nvidia.com> (raw)
Hi,
This series by Yevgeny brings several misc improvements to the mlx5 HWS
driver.
Regards,
Tariq
V3:
- Removed repeated log message in patch #1.
V2:
https://lore.kernel.org/all/20260810092630.3137666-1-tariqt@nvidia.com/
V1:
https://lore.kernel.org/all/20260723095349.1890983-1-tariqt@nvidia.com/
[timing] prompt build: 0s, prompt size: 13097 bytes
[timing] claude -p: 0s
[timing] line-wrap: 0s
Yevgeny Kliteynik (5):
net/mlx5: HWS, Print more details for bad completion
net/mlx5: HWS, Log syndrome on STC modify failure
net/mlx5: HWS, Set the num of queues only when alloc succeeded
net/mlx5: HWS, Remove redundant MLX5_SET in RTC creation
net/mlx5: HWS, Remove redundant FW command when reading caps
.../mellanox/mlx5/core/steering/hws/cmd.c | 15 ++---
.../mellanox/mlx5/core/steering/hws/send.c | 67 +++++++++++++------
2 files changed, 51 insertions(+), 31 deletions(-)
base-commit: e6a5d573d24cd375e09d24f136523cb3cc85c9d3
--
2.44.0
next reply other threads:[~2026-08-16 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 14:20 Tariq Toukan [this message]
2026-08-16 14:20 ` [PATCH net-next V3 1/5] net/mlx5: HWS, Print more details for bad completion Tariq Toukan
2026-08-16 14:20 ` [PATCH net-next V3 2/5] net/mlx5: HWS, Log syndrome on STC modify failure Tariq Toukan
2026-08-16 14:20 ` [PATCH net-next V3 3/5] net/mlx5: HWS, Set the num of queues only when alloc succeeded Tariq Toukan
2026-08-16 14:20 ` [PATCH net-next V3 4/5] net/mlx5: HWS, Remove redundant MLX5_SET in RTC creation Tariq Toukan
2026-08-16 14:20 ` [PATCH net-next V3 5/5] net/mlx5: HWS, Remove redundant FW command when reading caps Tariq Toukan
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=20260816142045.3289452-1-tariqt@nvidia.com \
--to=tariqt@nvidia.com \
--cc=agoldberger@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=erezsh@nvidia.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kees@kernel.org \
--cc=kliteyn@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 \
--cc=valex@nvidia.com \
--cc=vdogaru@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