From: patchwork-bot+netdevbpf@kernel.org
To: <Tristram.Ha@microchip.com>
Cc: woojung.huh@microchip.com, andrew@lunn.ch,
vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, UNGLinuxDriver@microchip.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
tristram.ha@microchip.com
Subject: Re: [PATCH v1 net] net: dsa: microchip: fix initial port flush problem
Date: Fri, 21 Jun 2024 02:40:27 +0000 [thread overview]
Message-ID: <171893762721.9082.9601801186482901167.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1718756202-2731-1-git-send-email-Tristram.Ha@microchip.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 18 Jun 2024 17:16:42 -0700 you wrote:
> From: Tristram Ha <tristram.ha@microchip.com>
>
> The very first flush in any port will flush all learned addresses in all
> ports. This can be observed by unplugging the cable from one port while
> additional ports are connected and dumping the fdb entries.
>
> This problem is caused by the initially wrong value programmed to the
> REG_SW_LUE_CTRL_1 register. Setting SW_FLUSH_STP_TABLE and
> SW_FLUSH_MSTP_TABLE bits does not have an immediate effect. It is when
> ksz9477_flush_dyn_mac_table() is called then the SW_FLUSH_STP_TABLE bit
> takes effect and flushes all learned entries. After that call both bits
> are reset and so the next port flush will not cause such problem again.
>
> [...]
Here is the summary with links:
- [v1,net] net: dsa: microchip: fix initial port flush problem
https://git.kernel.org/netdev/net/c/ad53f5f54f35
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:[~2024-06-21 2:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 0:16 [PATCH v1 net] net: dsa: microchip: fix initial port flush problem Tristram.Ha
2024-06-21 2: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=171893762721.9082.9601801186482901167.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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 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.