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, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/8] net: dsa: b53: add support for BCM5389/97/98 and BCM63XX ARL formats
Date: Tue, 11 Nov 2025 01:30:20 +0000 [thread overview]
Message-ID: <176282462024.2841507.15060077817611607078.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251107080749.26936-1-jonas.gorski@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 7 Nov 2025 09:07:41 +0100 you wrote:
> Currently b53 assumes that all switches apart from BCM5325/5365 use the
> same ARL formats, but there are actually multiple formats in use.
>
> Older switches use a format apparently introduced with BCM5387/BCM5389,
> while newer chips use a format apparently introduced with BCM5395.
>
> Note that these numbers are not linear, BCM5397/BCM5398 use the older
> format.
>
> [...]
Here is the summary with links:
- [net-next,1/8] net: dsa: b53: b53_arl_read{,25}(): use the entry for comparision
https://git.kernel.org/netdev/net-next/c/a6e4fd38bf2f
- [net-next,2/8] net: dsa: b53: move reading ARL entries into their own function
https://git.kernel.org/netdev/net-next/c/4a291fe72267
- [net-next,3/8] net: dsa: b53: move writing ARL entries into their own functions
https://git.kernel.org/netdev/net-next/c/bf6e9d2ae1db
- [net-next,4/8] net: dsa: b53: provide accessors for accessing ARL_SRCH_CTL
https://git.kernel.org/netdev/net-next/c/1716be6db04a
- [net-next,5/8] net: dsa: b53: split reading search entry into their own functions
https://git.kernel.org/netdev/net-next/c/e0c476f325a8
- [net-next,6/8] net: dsa: b53: move ARL entry functions into ops struct
https://git.kernel.org/netdev/net-next/c/a7e73339ad46
- [net-next,7/8] net: dsa: b53: add support for 5389/5397/5398 ARL entry format
https://git.kernel.org/netdev/net-next/c/300f78e8b6b7
- [net-next,8/8] net: dsa: b53: add support for bcm63xx ARL entry format
https://git.kernel.org/netdev/net-next/c/2b3013ac0302
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-11-11 1:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 8:07 [PATCH net-next 0/8] net: dsa: b53: add support for BCM5389/97/98 and BCM63XX ARL formats Jonas Gorski
2025-11-07 8:07 ` [PATCH net-next 1/8] net: dsa: b53: b53_arl_read{,25}(): use the entry for comparision Jonas Gorski
2025-11-08 0:39 ` Florian Fainelli
2025-11-07 8:07 ` [PATCH net-next 2/8] net: dsa: b53: move reading ARL entries into their own function Jonas Gorski
2025-11-08 0:40 ` Florian Fainelli
2025-11-07 8:07 ` [PATCH net-next 3/8] net: dsa: b53: move writing ARL entries into their own functions Jonas Gorski
2025-11-08 0:42 ` Florian Fainelli
2025-11-07 8:07 ` [PATCH net-next 4/8] net: dsa: b53: provide accessors for accessing ARL_SRCH_CTL Jonas Gorski
2025-11-08 0:42 ` Florian Fainelli
2025-11-07 8:07 ` [PATCH net-next 5/8] net: dsa: b53: split reading search entry into their own functions Jonas Gorski
2025-11-08 0:43 ` Florian Fainelli
2025-11-07 8:07 ` [PATCH net-next 6/8] net: dsa: b53: move ARL entry functions into ops struct Jonas Gorski
2025-11-08 0:43 ` Florian Fainelli
2025-11-07 8:07 ` [PATCH net-next 7/8] net: dsa: b53: add support for 5389/5397/5398 ARL entry format Jonas Gorski
2025-11-08 1:02 ` Florian Fainelli
2025-11-07 8:07 ` [PATCH net-next 8/8] net: dsa: b53: add support for bcm63xx " Jonas Gorski
2025-11-08 1:05 ` Florian Fainelli
2025-11-08 1:05 ` [PATCH net-next 0/8] net: dsa: b53: add support for BCM5389/97/98 and BCM63XX ARL formats Florian Fainelli
2025-11-11 1: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=176282462024.2841507.15060077817611607078.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.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=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