All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Linus Walleij" <linusw@kernel.org>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH net-next v4 5/5] net: dsa: ks8995: Delete surplus driver
Date: Wed, 03 Jun 2026 23:11:24 +0000	[thread overview]
Message-ID: <20260603231124.C719F1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260603-ks8995-to-ksz8-v4-5-e15149ef21e7@kernel.org>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] NET_DSA_KS8995 selects NET_DSA_MICROCHIP_KSZ_SPI without inheriting its required dependencies.
- [High] The transitional Kconfig option lacks a prompt and is defined as a `bool`, completely breaking the intended user migration.
--

commit b05792c06b27a646be1067e3e5c2643b8b180f96
Author: Linus Walleij <linusw@kernel.org>

net: dsa: ks8995: Delete surplus driver

This commit deletes the old ks8995 switch driver and replaces it with a
Kconfig stub. The stub is intended to transition users to the superseding
NET_DSA_MICROCHIP_KSZ_SPI driver automatically during config migration.

> diff --git a/drivers/net/dsa/Kconfig b/drivers/net/dsa/Kconfig
> index e704ab702c189..6a704b6383ffd 100644
> --- a/drivers/net/dsa/Kconfig
> +++ b/drivers/net/dsa/Kconfig
> @@ -98,13 +98,13 @@ config NET_DSA_RZN1_A5PSW
>  	  RZ/N1 SoC.
>  
>  config NET_DSA_KS8995
> -	tristate "Micrel KS8995 family 5-ports 10/100 Ethernet switches"
> -	depends on SPI
> -	depends on !NET_DSA_MICROCHIP_KSZ_SPI
> -	select NET_DSA_TAG_NONE
> +	bool

[Severity: High]
The commit message states this is a stub to automatically phase users
over to the new symbol when migrating their configs. However, without a
prompt string like bool "Transitional...", doesn't this become a hidden
symbol?

It looks like Kconfig will silently drop the old CONFIG_NET_DSA_KS8995
setting during make oldconfig rather than preserving the user's
selection, which would fail to migrate them to the new driver.

> +	select NET_DSA_MICROCHIP_KSZ_SPI

[Severity: High]
Will selecting NET_DSA_MICROCHIP_KSZ_SPI without inheriting its
dependencies cause unmet direct dependency warnings?

NET_DSA_MICROCHIP_KSZ_SPI depends on NET_DSA_MICROCHIP_KSZ_COMMON and
SPI, but these dependencies are not listed here. Could this lead to
build failures on configurations where the dependencies are not met?

>  	help
> -	  This driver supports the Micrel KS8995 family of 10/100 Mbit ethernet
> -	  switches, managed over SPI.
> +	  This is a transitional option for users who had NET_DSA_KS8995
> +	  enabled. It automatically enables the new NET_DSA_MICROCHIP_KSZ_SPI
> +	  driver which supersedes it. This option will be removed in a future
> +	  kernel release.
>  
>  config NET_DSA_SMSC_LAN9303
>  	tristate

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260603-ks8995-to-ksz8-v4-0-e15149ef21e7@kernel.org?part=5

      reply	other threads:[~2026-06-03 23:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02 23:10 [PATCH net-next v4 0/5] net: dsa: microchip: Add support for KSZ8995XA/KS8995XA Linus Walleij
2026-06-02 23:10 ` [PATCH net-next v4 1/5] net: dsa: microchip: Add fallback Micrel compatibles Linus Walleij
2026-06-03 23:11   ` sashiko-bot
2026-06-04  7:42     ` Linus Walleij
2026-06-02 23:10 ` [PATCH net-next v4 2/5] dt-bindings: net: dsa: microchip: Add KSZ8995XA Linus Walleij
2026-06-02 23:10 ` [PATCH net-next v4 3/5] net: dsa: tag_ks8995: Add the KS8995 tag handling Linus Walleij
2026-06-03 23:11   ` sashiko-bot
2026-06-02 23:10 ` [PATCH net-next v4 4/5] net: dsa: microchip: Support Microchip KSZ8995XA / KS8995XA Linus Walleij
2026-06-03 23:11   ` sashiko-bot
2026-06-04  8:09     ` Linus Walleij
2026-06-02 23:10 ` [PATCH net-next v4 5/5] net: dsa: ks8995: Delete surplus driver Linus Walleij
2026-06-03 23:11   ` sashiko-bot [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=20260603231124.C719F1F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linusw@kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.