From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
agoldberger@nvidia.com, valex@nvidia.com, cratiu@nvidia.com,
dtatulea@nvidia.com, erezsh@nvidia.com, gal@nvidia.com,
jacob.e.keller@intel.com, kees@kernel.org, leon@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
mbloch@nvidia.com, moshe@nvidia.com, saeedm@nvidia.com,
shayd@nvidia.com, horms@kernel.org, vdogaru@nvidia.com,
kliteyn@nvidia.com
Subject: Re: [PATCH net-next V3 0/5] net/mlx5: HWS misc enhancements
Date: Tue, 18 Aug 2026 02:00:13 +0000 [thread overview]
Message-ID: <178701841389.1828497.12446938123072918694.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260816142045.3289452-1-tariqt@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 16 Aug 2026 17:20:40 +0300 you wrote:
> Hi,
>
> This series by Yevgeny brings several misc improvements to the mlx5 HWS
> driver.
>
> Regards,
> Tariq
>
> [...]
Here is the summary with links:
- [net-next,V3,1/5] net/mlx5: HWS, Print more details for bad completion
https://git.kernel.org/netdev/net-next/c/dcb09aae194c
- [net-next,V3,2/5] net/mlx5: HWS, Log syndrome on STC modify failure
https://git.kernel.org/netdev/net-next/c/d4c34eebf18b
- [net-next,V3,3/5] net/mlx5: HWS, Set the num of queues only when alloc succeeded
https://git.kernel.org/netdev/net-next/c/5d3ff6671b62
- [net-next,V3,4/5] net/mlx5: HWS, Remove redundant MLX5_SET in RTC creation
https://git.kernel.org/netdev/net-next/c/7e34d2ada9c2
- [net-next,V3,5/5] net/mlx5: HWS, Remove redundant FW command when reading caps
https://git.kernel.org/netdev/net-next/c/bc502b3f69a3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-18 2:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 14:20 [PATCH net-next V3 0/5] net/mlx5: HWS misc enhancements Tariq Toukan
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
2026-08-18 2:00 ` patchwork-bot+netdevbpf [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=178701841389.1828497.12446938123072918694.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=tariqt@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