All of lore.kernel.org
 help / color / mirror / Atom feed
From: netdev-bot+sashiko@kernel.org
To: linusw@kernel.org
Cc: woojung.huh@microchip.com, UNGLinuxDriver@microchip.com,
	andrew@lunn.ch, olteanv@gmail.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	marex@denx.de, horms@kernel.org, linux@armlinux.org.uk,
	nb@tipi-net.de, netdev@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v9 1/4] dt-bindings: net: dsa: microchip: Add KSZ8995XA
Date: Tue, 08 Sep 2026 03:49:42 +0000	[thread overview]
Message-ID: <178883938242.219967.204339124922803087@kernel.org> (raw)
In-Reply-To: <20260906-ks8995-to-ksz8-v9-1-8d8815a91bd8@kernel.org>

Thank you for your contribution! Sashiko AI review found 1 potential
issue(s) to consider:

Critical: 0 · High: 0 · Medium: 0 · Low: 1

- [Low] Concern (verified as a FALSE POSITIVE by series validation): the
  new compatible `microchip,ksz8995xa` added to…

--

dt-bindings: net: dsa: microchip: Add KSZ8995XA

This adds a new compatible string microchip,ksz8995xa to the Microchip
KSZ switch family binding, described as having the same properties as
the older KS8995XA part. No other schema constraints are changed.

> diff --git a/Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml b/Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml
> index 8d4a3a9a33fcc..4ed13870ed3ac 100644
> --- a/Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml
> +++ b/Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml
> @@ -23,6 +23,7 @@ properties:
>        - microchip,ksz8864  # 4-port version of KSZ8895 family switch
>        - microchip,ksz8873
>        - microchip,ksz8895  # 5-port version of KSZ8895 family switch
> +      - microchip,ksz8995xa

[Severity: Low]
At this commit alone, is there any driver in tree that matches
microchip,ksz8995xa?  The existing part appears to be handled by the older
micrel,ks8995 binding and drivers/net/dsa/ks8995.c, so a device tree using
the new string would document a compatible that nothing binds to yet.

Checking the rest of the series, this looks already answered: the later
commit "net: dsa: microchip: Support Microchip KSZ8995XA / KS8995XA" adds

  drivers/net/dsa/microchip/ksz_spi.c:ksz_dt_ids
    { .compatible = "microchip,ksz8995xa",
      .data = &ksz_switch_chips[KSZ8995XA] },

along with ksz8995xa_regs[], ksz8995xa_dev_ops and ksz8995xa_switch_ops in
ksz_common.c, and "net: dsa: ks8995: Delete surplus driver" removes the
legacy driver and its micrel,* match table.  Documenting the binding one
patch ahead of the driver match entry is normal series ordering, so no
functional change results.

For completeness, the two if-then blocks in microchip,ksz.yaml (the
ksz8863/ksz8873 three-port block and the ksz8463 pinctrl/straps block) do
not appear to apply to this five-port part, so is it correct that neither
needs the new string added?

-- 
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260906-ks8995-to-ksz8-v9-0-8d8815a91bd8%40kernel.org

  reply	other threads:[~2026-09-08  3:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-06  7:48 [PATCH net-next v9 0/4] net: dsa: microchip: Add support for KSZ8995XA/KS8995XA Linus Walleij
2026-09-06  7:48 ` [PATCH net-next v9 1/4] dt-bindings: net: dsa: microchip: Add KSZ8995XA Linus Walleij
2026-09-08  3:49   ` netdev-bot+sashiko [this message]
2026-09-06  7:48 ` [PATCH net-next v9 2/4] net: dsa: tag_ks8995: Add the KS8995 tag handling Linus Walleij
2026-09-08  3:49   ` netdev-bot+sashiko
2026-09-06  7:48 ` [PATCH net-next v9 3/4] net: dsa: microchip: Support Microchip KSZ8995XA / KS8995XA Linus Walleij
2026-09-07  7:48   ` sashiko-bot
2026-09-08  3:49   ` netdev-bot+sashiko
2026-09-08  8:52     ` Linus Walleij
2026-09-06  7:48 ` [PATCH net-next v9 4/4] net: dsa: ks8995: Delete surplus driver Linus Walleij
2026-09-08  3:49   ` netdev-bot+sashiko
2026-09-08  9:18     ` Linus Walleij

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=178883938242.219967.204339124922803087@kernel.org \
    --to=netdev-bot+sashiko@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=marex@denx.de \
    --cc=nb@tipi-net.de \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    --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 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.