From: patchwork-bot+netdevbpf@kernel.org
To: Jonas Gorski <jonas.gorski@gmail.com>
Cc: florian.fainelli@broadcom.com, andrew@lunn.ch, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, noltari@gmail.com, f.fainelli@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/7] net: dsa: b53: fix ARL accesses for BCM5325/65 and allow VID 0
Date: Mon, 01 Dec 2025 22:50:19 +0000 [thread overview]
Message-ID: <176462941929.2581992.3926828060730665276.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251128080625.27181-1-jonas.gorski@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 28 Nov 2025 09:06:18 +0100 you wrote:
> ARL entries on BCM5325 and BCM5365 were broken significantly in two
> ways:
>
> - Entries for the CPU port were using the wrong port id, pointing to a
> non existing port.
> - Setting the VLAN ID for entries was not done, adding them all to VLAN
> 0 instead.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/7] net: dsa: b53: fix VLAN_ID_IDX write size for BCM5325/65
https://git.kernel.org/netdev/net-next/c/6f268e275c74
- [net-next,v2,2/7] net: dsa: b53: fix extracting VID from entry for BCM5325/65
https://git.kernel.org/netdev/net-next/c/9316012dd019
- [net-next,v2,3/7] net: dsa: b53: use same ARL search result offset for BCM5325/65
https://git.kernel.org/netdev/net-next/c/8e46aacea426
- [net-next,v2,4/7] net: dsa: b53: fix CPU port unicast ARL entries for BCM5325/65
https://git.kernel.org/netdev/net-next/c/85132103f700
- [net-next,v2,5/7] net: dsa: b53: fix BCM5325/65 ARL entry multicast port masks
https://git.kernel.org/netdev/net-next/c/3b08863469aa
- [net-next,v2,6/7] net: dsa: b53: fix BCM5325/65 ARL entry VIDs
https://git.kernel.org/netdev/net-next/c/d39514e6a2d1
- [net-next,v2,7/7] net: dsa: b53: allow VID 0 for BCM5325/65
https://git.kernel.org/netdev/net-next/c/0b2b27058692
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:[~2025-12-01 22:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 8:06 [PATCH net-next v2 0/7] net: dsa: b53: fix ARL accesses for BCM5325/65 and allow VID 0 Jonas Gorski
2025-11-28 8:06 ` [PATCH net-next v2 1/7] net: dsa: b53: fix VLAN_ID_IDX write size for BCM5325/65 Jonas Gorski
2025-11-28 8:06 ` [PATCH net-next v2 2/7] net: dsa: b53: fix extracting VID from entry " Jonas Gorski
2025-11-28 8:06 ` [PATCH net-next v2 3/7] net: dsa: b53: use same ARL search result offset " Jonas Gorski
2025-11-28 8:06 ` [PATCH net-next v2 4/7] net: dsa: b53: fix CPU port unicast ARL entries " Jonas Gorski
2025-12-01 1:29 ` Florian Fainelli
2025-11-28 8:06 ` [PATCH net-next v2 5/7] net: dsa: b53: fix BCM5325/65 ARL entry multicast port masks Jonas Gorski
2025-11-28 8:06 ` [PATCH net-next v2 6/7] net: dsa: b53: fix BCM5325/65 ARL entry VIDs Jonas Gorski
2025-12-01 1:30 ` Florian Fainelli
2025-11-28 8:06 ` [PATCH net-next v2 7/7] net: dsa: b53: allow VID 0 for BCM5325/65 Jonas Gorski
2025-12-01 1:31 ` Florian Fainelli
2025-12-01 22:50 ` 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=176462941929.2581992.3926828060730665276.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=jonas.gorski@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=olteanv@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).