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-next 0/3] mlx5 cleanups 2025-03-19
Date: Mon, 24 Mar 2025 20:50:39 +0000 [thread overview]
Message-ID: <174284943974.4167801.17963287974570911086.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1742412199-159596-1-git-send-email-tariqt@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 19 Mar 2025 21:23:16 +0200 you wrote:
> Hi,
>
> This series contains small cleanups to the mlx5 core and Eth drivers.
>
> Regards,
> Tariq
>
> [...]
Here is the summary with links:
- [net-next,1/3] net/mlx5: Remove NULL check before dev_{put, hold}
https://git.kernel.org/netdev/net-next/c/42cd8dee3a1b
- [net-next,2/3] net/mlx5e: Use right API to free bitmap memory
https://git.kernel.org/netdev/net-next/c/cac48eb6d383
- [net-next,3/3] net/mlx5e: Always select CONFIG_PAGE_POOL_STATS
https://git.kernel.org/netdev/net-next/c/cba38d1235ff
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 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 19:23 [PATCH net-next 0/3] mlx5 cleanups 2025-03-19 Tariq Toukan
2025-03-19 19:23 ` [PATCH net-next 1/3] net/mlx5: Remove NULL check before dev_{put, hold} Tariq Toukan
2025-03-20 4:29 ` Kalesh Anakkur Purayil
2025-03-19 19:23 ` [PATCH net-next 2/3] net/mlx5e: Use right API to free bitmap memory Tariq Toukan
2025-03-20 4:28 ` Kalesh Anakkur Purayil
2025-03-19 19:23 ` [PATCH net-next 3/3] net/mlx5e: Always select CONFIG_PAGE_POOL_STATS Tariq Toukan
2025-03-24 20:50 ` 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=174284943974.4167801.17963287974570911086.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox