From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, andrew+netdev@lunn.ch, gal@nvidia.com,
leonro@nvidia.com, saeedm@nvidia.com, leon@kernel.org,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, moshe@nvidia.com,
mbloch@nvidia.com
Subject: Re: [PATCH net 0/2] mlx5 misc fixes 2025-03-18
Date: Mon, 24 Mar 2025 22:30:33 +0000 [thread overview]
Message-ID: <174285543328.6006.16335198386099285028.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1742331077-102038-1-git-send-email-tariqt@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 18 Mar 2025 22:51:15 +0200 you wrote:
> Hi,
>
> This small patchset provides misc bug fixes to the mlx5 core driver.
>
> Thanks,
> Tariq.
>
> [...]
Here is the summary with links:
- [net,1/2] net/mlx5: LAG, reload representors on LAG creation failure
https://git.kernel.org/netdev/net/c/bdf549a7a4d7
- [net,2/2] net/mlx5: Start health poll after enable hca
https://git.kernel.org/netdev/net/c/1726ad035cb0
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:[~2025-03-24 22:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 20:51 [PATCH net 0/2] mlx5 misc fixes 2025-03-18 Tariq Toukan
2025-03-18 20:51 ` [PATCH net 1/2] net/mlx5: LAG, reload representors on LAG creation failure Tariq Toukan
2025-03-19 7:13 ` Michal Swiatkowski
2025-03-19 11:36 ` Kalesh Anakkur Purayil
2025-03-18 20:51 ` [PATCH net 2/2] net/mlx5: Start health poll after enable hca Tariq Toukan
2025-03-19 9:36 ` Michal Swiatkowski
2025-03-19 11:35 ` Kalesh Anakkur Purayil
2025-03-24 22:30 ` 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=174285543328.6006.16335198386099285028.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=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.