From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: configs: sama5: enable current Microchip KSZ DSA symbols
Date: Sat, 19 Sep 2026 17:38:02 +0300 [thread overview]
Message-ID: <c55123de-f466-41c8-b50e-df28ecf3bc18@tuxon.dev> (raw)
In-Reply-To: <20260814075310.11613-1-pengpeng@iscas.ac.cn>
On 8/14/26 10:53, Pengpeng Hou wrote:
> The Microchip KSZ DSA family now uses NET_DSA_MICROCHIP_KSZ_COMMON
> for the common provider and NET_DSA_MICROCHIP_KSZ_SPI for SPI-attached
> switches.
>
> sama5_defconfig still enables the removed KSZ9477-specific symbols even
> though SAMA5 device trees contain KSZ SPI switch consumers. Replace the
> stale entries with the current provider symbols.
>
> Assisted-by: Codex:gpt-5
> Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
Fixes: 07bca160469b ("net: dsa: microchip: common menuconfig for ksz series switch")
Fixes: 4658f2fe8fbc ("net: dsa: microchip: common ksz_spi_probe for ksz switches")
Reviewed-by: Claudiu Beznea <claudiu.beznea@tuxon.dev>
> ---
> Changes since v1: https://lore.kernel.org/all/20260624081216.75559-1-pengpeng@iscas.ac.cn/
> - no source-code changes
> - rebase on the current SAMA5 defconfig
> - route the revision to the AT91 SoC maintainers
> - add the coding-assistant disclosure
>
> The Kconfig/provider mapping was reviewed statically; no SAMA5 kernel build
> was performed.
>
> arch/arm/configs/sama5_defconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/configs/sama5_defconfig b/arch/arm/configs/sama5_defconfig
> index bd7f0b5f7d66..46e7f554faa1 100644
> --- a/arch/arm/configs/sama5_defconfig
> +++ b/arch/arm/configs/sama5_defconfig
> @@ -70,8 +70,8 @@ CONFIG_BLK_DEV_SD=y
> # CONFIG_BLK_DEV_BSG is not set
> # CONFIG_SCSI_LOWLEVEL is not set
> CONFIG_NETDEVICES=y
> -CONFIG_NET_DSA_MICROCHIP_KSZ9477=m
> -CONFIG_NET_DSA_MICROCHIP_KSZ9477_SPI=m
> +CONFIG_NET_DSA_MICROCHIP_KSZ_COMMON=m
> +CONFIG_NET_DSA_MICROCHIP_KSZ_SPI=m
> # CONFIG_NET_VENDOR_BROADCOM is not set
> CONFIG_MACB=y
> # CONFIG_NET_VENDOR_CIRRUS is not set
next prev parent reply other threads:[~2026-09-19 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 7:53 Pengpeng Hou
2026-09-19 14:38 ` claudiu beznea [this message]
2026-09-20 3:09 ` Pengpeng Hou
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=c55123de-f466-41c8-b50e-df28ecf3bc18@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nicolas.ferre@microchip.com \
--cc=pengpeng@iscas.ac.cn \
/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
all inboxes | Powered by JetHome®