public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: linusw@kernel.org
Cc: Jakub Kicinski <kuba@kernel.org>,
	olteanv@gmail.com, pabeni@redhat.com, davem@davemloft.net,
	woojung.huh@microchip.com, andrew@lunn.ch,
	UNGLinuxDriver@microchip.com, netdev@vger.kernel.org,
	edumazet@google.com
Subject: Re: [net-next,v2,2/4] net: dsa: ks8955: Delete KSZ8864 and KSZ8795 support
Date: Mon, 19 Jan 2026 08:34:10 -0800	[thread overview]
Message-ID: <20260119163410.1147227-1-kuba@kernel.org> (raw)
In-Reply-To: <20260119-ks8995-fixups-v2-2-98bd034a0d12@kernel.org>

This is an AI-generated review of your patch. The human sending this
email has considered the AI review valid, or at least plausible.

For local reproduction steps see https://netdev-ai.bots.linux.dev/ai-local.html
---
net: dsa: ks8955: Delete KSZ8864 and KSZ8795 support

This commit removes support for KSZ8864 and KSZ8795 chip variants from
the ks8995 driver, since those variants are better supported by the
dedicated Microchip KSZ driver.

> diff --git a/drivers/net/dsa/ks8995.c b/drivers/net/dsa/ks8995.c
> index ff01097601ec..5ad62fa4e52c 100644
> --- a/drivers/net/dsa/ks8995.c
> +++ b/drivers/net/dsa/ks8995.c

[ ... ]

> @@ -804,8 +700,8 @@ static int ks8995_probe(struct spi_device *spi)
>  	if (err)
>  		return err;
>
> -	dev_info(&spi->dev, "%s device found, Chip ID:%x, Revision:%x\n",
> -		 ks->chip->name, ks->chip->chip_id, ks->revision_id);
> +	dev_info(&spi->dev, "KS8955MA device found, Chip ID:%x, Revision:%x\n",
                             ^^^^^^^

Should this be "KS8995MA" instead of "KS8955MA"? The chip name appears to
have a typo - the driver is for KS8995 (as in the file name, module
description, and all other references), but the dev_info prints "KS8955MA"
with transposed digits.

> +		 KS8995_CHIP_ID, ks->revision_id);
-- 
pw-bot: cr

  reply	other threads:[~2026-01-19 16:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 14:30 [PATCH net-next v2 0/4] net: dsa: ks8995: Post-move fixes Linus Walleij
2026-01-19 14:30 ` [PATCH net-next v2 1/4] net: dsa: ks8995: Add shutdown callback Linus Walleij
2026-01-19 15:38   ` Vladimir Oltean
2026-01-19 16:33     ` Jakub Kicinski
2026-01-19 16:40       ` Vladimir Oltean
2026-01-19 20:26       ` Linus Walleij
2026-01-19 14:30 ` [PATCH net-next v2 2/4] net: dsa: ks8955: Delete KSZ8864 and KSZ8795 support Linus Walleij
2026-01-19 16:34   ` Jakub Kicinski [this message]
2026-01-19 21:58   ` Vladimir Oltean
2026-01-19 23:26     ` Linus Walleij
2026-01-19 14:30 ` [PATCH net-next v2 3/4] net: dsa: ks8995: Add stub bridge join/leave Linus Walleij
2026-01-19 22:20   ` Vladimir Oltean
2026-01-19 14:30 ` [PATCH net-next v2 4/4] net: dsa: ks8995: Implement port isolation Linus Walleij
2026-01-19 22:48   ` Vladimir Oltean

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=20260119163410.1147227-1-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=linusw@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=woojung.huh@microchip.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