From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
agoldberger@nvidia.com, gal@nvidia.com, leon@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
mbloch@nvidia.com, saeedm@nvidia.com, shayd@nvidia.com,
horms@kernel.org
Subject: Re: [PATCH net] net/mlx5: IFC, enlarge active_port field to support 8 port LAG
Date: Tue, 17 Nov 2026 02:50:05 +0000 [thread overview]
Message-ID: <179488380528.305876.11658073225104873930.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261112182940.3655773-1-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 12 Nov 2026 20:29:40 +0200 you wrote:
> From: Shay Drory <shayd@nvidia.com>
>
> active_port is a bitmask with a bit per LAG port. The cited commit
> enabled 8 port LAG, but active_port remained 4 bits wide.
>
> Enlarge active_port to 8 bits, as defined in the PRM.
>
> [...]
Here is the summary with links:
- [net] net/mlx5: IFC, enlarge active_port field to support 8 port LAG
https://git.kernel.org/netdev/net/c/a2239d5dbbda
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:[~2026-11-17 2:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 18:29 [PATCH net] net/mlx5: IFC, enlarge active_port field to support 8 port LAG Tariq Toukan
2026-11-13 15:27 ` sashiko-bot
2026-11-13 15:27 ` netdev-bot+sinfo
2026-11-15 11:26 ` Shay Drory
2026-11-17 2: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=179488380528.305876.11658073225104873930.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=agoldberger@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--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=saeedm@nvidia.com \
--cc=shayd@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.