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, saeed@kernel.org,
gal@nvidia.com, leon@kernel.org, saeedm@nvidia.com,
mbloch@nvidia.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next V2 0/2] net/mlx5e: misc changes 2025-07-22
Date: Fri, 25 Jul 2025 23:26:08 +0000 [thread overview]
Message-ID: <175348596874.3366157.1851512921541763037.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1753194228-333722-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 Tue, 22 Jul 2025 17:23:46 +0300 you wrote:
> Hi,
>
> This series contains misc enhancements to the mlx5e driver.
> This is V2. Previous one was deferred, find it here:
> https://lore.kernel.org/all/1752771792-265762-1-git-send-email-tariqt@nvidia.com/
>
> Regards,
> Tariq
>
> [...]
Here is the summary with links:
- [net-next,V2,1/2] net/mlx5e: Support routed networks during IPsec MACs initialization
https://git.kernel.org/netdev/net-next/c/71670f766b8f
- [net-next,V2,2/2] net/mlx5e: Expose TIS via devlink tx reporter diagnose
https://git.kernel.org/netdev/net-next/c/5474ca211819
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-07-25 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 14:23 Tariq Toukan
2025-07-22 14:23 ` [PATCH net-next V2 1/2] net/mlx5e: Support routed networks during IPsec MACs initialization Tariq Toukan
2025-07-23 6:52 ` Michal Swiatkowski
2025-07-23 7:10 ` Leon Romanovsky
2025-07-22 14:23 ` [PATCH net-next V2 2/2] net/mlx5e: Expose TIS via devlink tx reporter diagnose Tariq Toukan
2025-07-23 6:56 ` Michal Swiatkowski
2025-07-25 23:26 ` 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=175348596874.3366157.1851512921541763037.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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--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®