[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166076401518.21609.10073950872734120316.git-patchwork-notify@kernel.org>
Date: Wed, 17 Aug 2022 19:20:15 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Arun Ramadoss <arun.ramadoss@...rochip.com>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
woojung.huh@...rochip.com, UNGLinuxDriver@...rochip.com,
andrew@...n.ch, vivien.didelot@...il.com, f.fainelli@...il.com,
olteanv@...il.com, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, linux@...linux.org.uk,
Tristram.Ha@...rochip.com
Subject: Re: [patch net v3] net: dsa: microchip: ksz9477: fix fdb_dump last
invalid entry
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 16 Aug 2022 16:25:16 +0530 you wrote:
> In the ksz9477_fdb_dump function it reads the ALU control register and
> exit from the timeout loop if there is valid entry or search is
> complete. After exiting the loop, it reads the alu entry and report to
> the user space irrespective of entry is valid. It works till the valid
> entry. If the loop exited when search is complete, it reads the alu
> table. The table returns all ones and it is reported to user space. So
> bridge fdb show gives ff:ff:ff:ff:ff:ff as last entry for every port.
> To fix it, after exiting the loop the entry is reported only if it is
> valid one.
>
> [...]
Here is the summary with links:
- [net,v3] net: dsa: microchip: ksz9477: fix fdb_dump last invalid entry
https://git.kernel.org/netdev/net/c/36c0d9350157
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists