From: patchwork-bot+netdevbpf@kernel.org
To: Edoardo Pinci <epinci@outlook.com>
Cc: netdev@vger.kernel.org, daniel@makrotopia.org
Subject: Re: [PATCH net v2] net: dsa: mxl862xx: enable assisted learning on CPU port
Date: Thu, 27 Aug 2026 19:40:27 +0000 [thread overview]
Message-ID: <178785962789.1816627.5162200270683256068.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <DU0P251MB069949C6DEB4D1D51F31FE87C4A02@DU0P251MB0699.EURP251.PROD.OUTLOOK.COM>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 24 Aug 2026 15:11:43 +0200 you wrote:
> The MxL862xx driver enables FDB isolation but does not enable assisted
> learning on the CPU port. Consequently, MAC addresses learned through a
> physical switch port are not updated in hardware when the corresponding
> station moves to a foreign bridge port, such as a Wi-Fi interface.
>
> The stale hardware FDB entry continues directing return traffic toward
> the original physical port. Traffic entering that same port is then
> filtered instead of being forwarded to the CPU and software bridge. This
> causes downstream unicast traffic, including DHCP OFFER and ACK packets,
> to disappear after a client roams to a local wireless interface. The
> client eventually considers the connection unusable and disconnects.
>
> [...]
Here is the summary with links:
- [net,v2] net: dsa: mxl862xx: enable assisted learning on CPU port
https://git.kernel.org/netdev/net/c/88c71cc0ad98
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-08-27 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 13:11 [PATCH net v2] net: dsa: mxl862xx: enable assisted learning on CPU port Edoardo Pinci
2026-08-27 19:40 ` 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=178785962789.1816627.5162200270683256068.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=daniel@makrotopia.org \
--cc=epinci@outlook.com \
--cc=netdev@vger.kernel.org \
/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.