From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Machon <daniel.machon@microchip.com>
Cc: horatiu.vultur@microchip.com, UNGLinuxDriver@microchip.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: lan966x: do not warn on MAC entries that are not port destined
Date: Tue, 27 Oct 2026 14:30:05 +0000 [thread overview]
Message-ID: <179311140532.3859410.11214781707545334136.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261026-lan966x-mac-warn-v1-1-9c885f9cbda9@microchip.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 26 Oct 2026 14:46:28 +0100 you wrote:
> lan966x_mac_irq_handler() scans the rows of the MAC table that the
> analyzer reports as changed, reads back all four columns of each row and
> treats ANA_MACACCESS.DEST_IDX as a port number.
>
> Before this patch, a destination index above num_phys_ports hits a
> WARN_ON(). The driver installs such entries itself:
> lan966x_mac_cpu_learn() uses PGID_CPU, and L2 multicast entries use a
> general-purpose PGID. A row holding one of them is read back whenever
> another entry in the same row is learned or aged out, so the scan warns
> in normal operation, repeatedly once the MAC table is busy.
>
> [...]
Here is the summary with links:
- [net] net: lan966x: do not warn on MAC entries that are not port destined
https://git.kernel.org/netdev/net/c/2cffcf1aeabb
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-10-27 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 13:46 [PATCH net] net: lan966x: do not warn on MAC entries that are not port destined Daniel Machon
2026-10-27 14:30 ` 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=179311140532.3859410.11214781707545334136.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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