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,
mbloch@nvidia.com, leon@kernel.org, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
gal@nvidia.com, moshe@nvidia.com
Subject: Re: [PATCH net 0/3] mlx5 misc fixes 2025-09-22
Date: Wed, 24 Sep 2025 00:20:15 +0000 [thread overview]
Message-ID: <175867321524.1971872.14099732111728782116.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1758525094-816583-1-git-send-email-tariqt@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 22 Sep 2025 10:11:31 +0300 you wrote:
> Hi,
>
> This patchset provides misc bug fixes from the team to the mlx5 Eth
> and core drivers.
>
> Thanks,
> Tariq.
>
> [...]
Here is the summary with links:
- [net,1/3] net/mlx5: fs, fix UAF in flow counter release
https://git.kernel.org/netdev/net/c/6043819e707c
- [net,2/3] net/mlx5: HWS, ignore flow level for multi-dest table
https://git.kernel.org/netdev/net/c/efb877cf27e3
- [net,3/3] net/mlx5e: Fix missing FEC RS stats for RS_544_514_INTERLEAVED_QUAD
https://git.kernel.org/netdev/net/c/6d0477d0d067
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-09-24 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 7:11 Tariq Toukan
2025-09-22 7:11 ` [PATCH net 1/3] net/mlx5: fs, fix UAF in flow counter release Tariq Toukan
2025-09-22 7:11 ` [PATCH net 2/3] net/mlx5: HWS, ignore flow level for multi-dest table Tariq Toukan
2025-09-22 7:11 ` [PATCH net 3/3] net/mlx5e: Fix missing FEC RS stats for RS_544_514_INTERLEAVED_QUAD Tariq Toukan
2025-09-24 0: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=175867321524.1971872.14099732111728782116.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=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
all inboxes | Powered by JetHome®