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 v14 1/4] dt-bindings: net: dsa: microchip: Add KSZ8995XA
Date: Tue, 15 Sep 2026 23:36:46 +0000 [thread overview]
Message-ID: <178951540672.22033.5965330247410897822@kernel.org> (raw)
In-Reply-To: <20260914-ks8995-to-ksz8-v14-1-3d72692b3c97@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 (validated as resolved within the series): the new
compatible `microchip,ksz8995xa` added to…
--
dt-bindings: net: dsa: microchip: Add KSZ8995XA
Adds the compatible string microchip,ksz8995xa to the Microchip KSZ
series DSA switch binding, described as having the same properties as
the KS8995XA. No Link: tags were present in the commit header.
> 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]
One thing that came up while reviewing this in isolation: at this commit
there is no consumer for microchip,ksz8995xa, so a device tree using it
would not match anything in ksz_dt_ids[] in
drivers/net/dsa/microchip/ksz_spi.c and ksz_spi_probe() would bail out.
Checking the rest of the series resolves this, so this looks fine as is:
drivers/net/dsa/microchip/ksz_spi.c:ksz_dt_ids[]
{
.compatible = "microchip,ksz8995xa",
.data = &ksz_switch_chips[KSZ8995XA]
},
drivers/net/dsa/microchip/ksz_spi.c:ksz_spi_ids[]
{ "ksz8995xa" },
along with the ksz8995xa_regs[] register map and the KSZ8995XA entry in
ksz_switch_chips[] in drivers/net/dsa/microchip/ksz_common.c, all added by
"net: dsa: microchip: Support Microchip KSZ8995XA / KS8995XA". The
alternative placement in micrel,ks8995.yaml also does not apply since
drivers/net/dsa/ks8995.c is removed by "net: dsa: ks8995: Delete surplus
driver" in the same series.
Should the placement of the compatible with respect to the existing
allOf/if blocks be double checked too? The microchip,ksz8863/ksz8873
3-port block and the microchip,ksz8463 straps block both look inapplicable
to a 5-port KSZ8995XA, so as far as I can tell no existing conditional
needed the new string added, but confirmation would be useful.
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260914-ks8995-to-ksz8-v14-0-3d72692b3c97%40kernel.org
next prev parent reply other threads:[~2026-09-15 23:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 20:35 [PATCH net-next v14 0/4] net: dsa: microchip: Add support for KSZ8995XA/KS8995XA Linus Walleij
2026-09-14 20:35 ` [PATCH net-next v14 1/4] dt-bindings: net: dsa: microchip: Add KSZ8995XA Linus Walleij
2026-09-15 23:36 ` netdev-bot+sashiko [this message]
2026-09-14 20:35 ` [PATCH net-next v14 2/4] net: dsa: tag_ks8995: Add the KS8995 tag handling Linus Walleij
2026-09-15 20:35 ` sashiko-bot
2026-09-15 23:21 ` Linus Walleij
2026-09-14 20:35 ` [PATCH net-next v14 3/4] net: dsa: microchip: Support Microchip KSZ8995XA / KS8995XA Linus Walleij
2026-09-15 20:35 ` sashiko-bot
2026-09-15 23:36 ` netdev-bot+sashiko
2026-09-14 20:35 ` [PATCH net-next v14 4/4] net: dsa: ks8995: Delete surplus driver Linus Walleij
2026-09-15 23:36 ` netdev-bot+sashiko
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=178951540672.22033.5965330247410897822@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.