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, saeedm@nvidia.com,
gal@nvidia.com, leonro@nvidia.com,
michal.swiatkowski@linux.intel.com, leon@kernel.org,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next V2 0/6] mlx5 misc enhancements 2025-03-04
Date: Fri, 07 Mar 2025 02:30:41 +0000 [thread overview]
Message-ID: <174131464148.1860023.2397596403061740180.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250304160620.417580-1-tariqt@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 4 Mar 2025 18:06:14 +0200 you wrote:
> Hi,
>
> This is V2.
> Find initial version here:
> https://lore.kernel.org/lkml/20250226114752.104838-1-tariqt@nvidia.com/
>
> This series introduces enhancements to the mlx5 core and Eth drivers.
>
> [...]
Here is the summary with links:
- [net-next,V2,1/6] net/mlx5: Relocate function declarations from port.h to mlx5_core.h
https://git.kernel.org/netdev/net-next/c/a2f61f1db855
- [net-next,V2,2/6] net/mlx5: Refactor link speed handling with mlx5_link_info struct
https://git.kernel.org/netdev/net-next/c/65a5d3557184
- [net-next,V2,3/6] net/mlx5e: Enable lanes configuration when auto-negotiation is off
https://git.kernel.org/netdev/net-next/c/7e959797f021
- [net-next,V2,4/6] net/mlx5: Lag, Enable Multiport E-Switch offloads on 8 ports LAG
https://git.kernel.org/netdev/net-next/c/5aa2e6de86d5
- [net-next,V2,5/6] net/mlx5e: Separate address related variables to be in struct
https://git.kernel.org/netdev/net-next/c/348ed4b20546
- [net-next,V2,6/6] net/mlx5e: Properly match IPsec subnet addresses
https://git.kernel.org/netdev/net-next/c/ca7992f52c2c
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-07 2:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 16:06 [PATCH net-next V2 0/6] mlx5 misc enhancements 2025-03-04 Tariq Toukan
2025-03-04 16:06 ` [PATCH net-next V2 1/6] net/mlx5: Relocate function declarations from port.h to mlx5_core.h Tariq Toukan
2025-03-04 16:06 ` [PATCH net-next V2 2/6] net/mlx5: Refactor link speed handling with mlx5_link_info struct Tariq Toukan
2025-03-04 16:06 ` [PATCH net-next V2 3/6] net/mlx5e: Enable lanes configuration when auto-negotiation is off Tariq Toukan
2025-03-04 16:06 ` [PATCH net-next V2 4/6] net/mlx5: Lag, Enable Multiport E-Switch offloads on 8 ports LAG Tariq Toukan
2025-03-04 16:06 ` [PATCH net-next V2 5/6] net/mlx5e: Separate address related variables to be in struct Tariq Toukan
2025-03-04 16:06 ` [PATCH net-next V2 6/6] net/mlx5e: Properly match IPsec subnet addresses Tariq Toukan
2025-03-07 2: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=174131464148.1860023.2397596403061740180.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=michal.swiatkowski@linux.intel.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