From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@kernel.org, andrew+netdev@lunn.ch,
petrm@nvidia.com
Subject: Re: [PATCH net-next] mlxsw: Disable LAG collector when requested
Date: Thu, 12 Nov 2026 19:20:10 +0000 [thread overview]
Message-ID: <179451121002.604801.11604496197822603809.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261111170925.2809513-1-idosch@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 11 Nov 2026 19:09:25 +0200 you wrote:
> mlxsw_reg_slcor_col_disable_pack() packs the "collector enabled" value
> instead of "collector disabled". As a result, once a LAG port is enabled
> for collection, it keeps receiving packets even after the LAG master
> disables it (e.g., when the port loses link or the LACP partner falls
> out of sync).
>
> Fix by packing the correct value. Packets received on a disabled LAG
> port are now dropped, as they are in the bond's software datapath.
>
> [...]
Here is the summary with links:
- [net-next] mlxsw: Disable LAG collector when requested
https://git.kernel.org/netdev/net-next/c/073d54dc3ccc
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-12 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 17:09 [PATCH net-next] mlxsw: Disable LAG collector when requested Ido Schimmel
2026-11-12 17:17 ` netdev-bot+sashiko
2026-11-12 19: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=179451121002.604801.11604496197822603809.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@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.