From: Oleksij Rempel <o.rempel@pengutronix.de>
To: netdev-bot+sashiko@kernel.org
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 v2 3/3] net: dsa: forget the port ageing time when the port leaves the bridge
Date: Tue, 17 Nov 2026 13:02:24 +0100 [thread overview]
Message-ID: <avxCUGkgmY9l2kho@pengutronix.de> (raw)
In-Reply-To: <179482683686.3136.4297608809022872177@kernel.org>
On Mon, Nov 16, 2026 at 11:00:36AM +0000, netdev-bot+sashiko@kernel.org wrote:
> Could the leave path recompute the fastest ageing time over the
> switch's remaining bridged ports after clearing the cache, and program
> it?
Yes, I reproduced this on a KSZ9893 with two bridges. v3 adds a patch
that programs the fastest ageing time of the remaining bridged ports
when a port leaves its bridge.
pw-bot: cr
prev parent reply other threads:[~2026-11-17 12:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 10:59 [PATCH net-next v2 0/3] net: dsa: make a shorter bridge ageing time take effect Oleksij Rempel
2026-11-15 10:59 ` [PATCH net-next v2 1/3] net: dsa: microchip: ksz9477: apply a shorter ageing time at once Oleksij Rempel
2026-11-15 15:38 ` Andrew Lunn
2026-11-16 11:00 ` netdev-bot+sashiko
2026-11-17 11:59 ` Oleksij Rempel
2026-11-15 10:59 ` [PATCH net-next v2 2/3] net: dsa: ignore the old ageing time of the port being changed Oleksij Rempel
2026-11-15 15:40 ` Andrew Lunn
2026-11-15 10:59 ` [PATCH net-next v2 3/3] net: dsa: forget the port ageing time when the port leaves the bridge Oleksij Rempel
2026-11-15 15:40 ` Andrew Lunn
2026-11-16 11:00 ` netdev-bot+sashiko
2026-11-17 12:02 ` Oleksij Rempel [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=avxCUGkgmY9l2kho@pengutronix.de \
--to=o.rempel@pengutronix.de \
--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-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--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
all inboxes | Powered by JetHome®