From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
andrew+netdev@lunn.ch, davem@davemloft.net, saeedm@nvidia.com,
leon@kernel.org, mbloch@nvidia.com, shayd@nvidia.com,
shayag@mellanox.com, saeedm@mellanox.com, jianbol@nvidia.com,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, gal@nvidia.com
Subject: Re: [PATCH net 0/3] mlx5 misc fixes 2026-03-30
Date: Thu, 02 Apr 2026 03:20:15 +0000 [thread overview]
Message-ID: <177510001504.3972881.18083419303971331351.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260330194015.53585-1-tariqt@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 30 Mar 2026 22:40:12 +0300 you wrote:
> Hi,
>
> This patchset provides misc bug fixes from the team to the mlx5
> core driver.
>
> Thanks,
> Tariq.
>
> [...]
Here is the summary with links:
- [net,1/3] net/mlx5: lag: Check for LAG device before creating debugfs
https://git.kernel.org/netdev/net/c/bf16bca66536
- [net,2/3] net/mlx5: Avoid "No data available" when FW version queries fail
https://git.kernel.org/netdev/net/c/10dc35f6a443
- [net,3/3] net/mlx5: Fix switchdev mode rollback in case of failure
https://git.kernel.org/netdev/net/c/403186400a1a
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-04-02 3:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 19:40 [PATCH net 0/3] mlx5 misc fixes 2026-03-30 Tariq Toukan
2026-03-30 19:40 ` [PATCH net 1/3] net/mlx5: lag: Check for LAG device before creating debugfs Tariq Toukan
2026-03-30 19:40 ` [PATCH net 2/3] net/mlx5: Avoid "No data available" when FW version queries fail Tariq Toukan
2026-03-30 19:40 ` [PATCH net 3/3] net/mlx5: Fix switchdev mode rollback in case of failure Tariq Toukan
2026-04-02 3:20 ` 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=177510001504.3972881.18083419303971331351.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=jianbol@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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@mellanox.com \
--cc=saeedm@nvidia.com \
--cc=shayag@mellanox.com \
--cc=shayd@nvidia.com \
--cc=tariqt@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