From: patchwork-bot+netdevbpf@kernel.org
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: woojung.huh@microchip.com, UNGLinuxDriver@microchip.com,
andrew@lunn.ch, olteanv@gmail.com, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, arun.ramadoss@microchip.com, jiri@resnulli.us,
linusw@kernel.org, f.fainelli@gmail.com,
vivien.didelot@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
jensemil.schulzostergaard@microchip.com
Subject: Re: [PATCH net-next v3 0/3] net: dsa: make a shorter bridge ageing time take effect
Date: Sat, 21 Nov 2026 00:20:05 +0000 [thread overview]
Message-ID: <179522040578.853171.11730674310408449744.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261117-ksz-stp-ageing-v3-0-135de6b9f8ad@pengutronix.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 17 Nov 2026 14:02:10 +0100 you wrote:
> During an STP topology change, the bridge lowers the ageing time so
> that stale FDB entries go away quickly. When the change is over, the
> bridge sets the configured value again. On DSA switches, both steps
> can go wrong:
>
> - On a KSZ9893, ksz9477 does not apply a shorter value at once. Patch 1
> fixes this.
> - The DSA core can keep the short value after the bridge has restored
> the long one. Patch 2 fixes this, and patch 3 does the same for a
> port that has left the bridge.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/3] net: dsa: microchip: ksz9477: apply a shorter ageing time at once
https://git.kernel.org/netdev/net-next/c/bf18142882a0
- [net-next,v3,2/3] net: dsa: ignore the old ageing time of the port being changed
https://git.kernel.org/netdev/net-next/c/133927a00589
- [net-next,v3,3/3] net: dsa: forget the port ageing time when the port leaves the bridge
https://git.kernel.org/netdev/net-next/c/eb0431e3f3e4
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-21 0:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 13:02 [PATCH net-next v3 0/3] net: dsa: make a shorter bridge ageing time take effect Oleksij Rempel
2026-11-17 13:02 ` [PATCH net-next v3 1/3] net: dsa: microchip: ksz9477: apply a shorter ageing time at once Oleksij Rempel
2026-11-19 1:03 ` netdev-bot+sashiko
2026-11-19 7:19 ` Oleksij Rempel
2026-11-17 13:02 ` [PATCH net-next v3 2/3] net: dsa: ignore the old ageing time of the port being changed Oleksij Rempel
2026-11-17 21:37 ` Linus Walleij
2026-11-17 13:02 ` [PATCH net-next v3 3/3] net: dsa: forget the port ageing time when the port leaves the bridge Oleksij Rempel
2026-11-19 1:03 ` netdev-bot+sashiko
2026-11-19 7:23 ` Oleksij Rempel
2026-11-21 0: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=179522040578.853171.11730674310408449744.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=horms@kernel.org \
--cc=jensemil.schulzostergaard@microchip.com \
--cc=jiri@resnulli.us \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@microchip.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