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: [net-next,v8,2/5] dt-bindings: net: dsa: microchip: Add KSZ8995XA
Date: Wed, 02 Sep 2026 09:50:37 +0000 [thread overview]
Message-ID: <178834263728.3394541.8763382902139129360@kernel.org> (raw)
In-Reply-To: <20260831-ks8995-to-ksz8-v8-2-fd1dbb2b76e8@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 FALSE POSITIVE by series-end verification):
the newly documented `microchip,ksz8995xa` compatible was reported to…
--
dt-bindings: net: dsa: microchip: Add KSZ8995XA
This adds a new compatible string microchip,ksz8995xa to the Microchip KSZ
switch binding, noting the part was renamed from KS8995XA and that
KSZ8995MA and KSZ8995E are different parts.
> 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, is there anything in tree that matches this compatible?
A device tree node using microchip,ksz8995xa passes dt_binding_check here,
but ksz_dt_ids[] in drivers/net/dsa/microchip/ksz_spi.c has no entry for
it yet, so the node would not probe.
That said, the following patch in the same series ("net: dsa: microchip:
Support Microchip KSZ8995XA / KS8995XA") adds the matching entry:
drivers/net/dsa/microchip/ksz_spi.c:ksz_dt_ids[] {
...
{
.compatible = "microchip,ksz8995xa",
.data = &ksz_switch_chips[KSZ8995XA]
},
...
}
along with ksz_switch_chips[KSZ8995XA] and the { "ksz8995" } spi_device_id
entry, so at the tip of the series the string does resolve to a driver.
Documenting the binding ahead of the driver is the usual ordering, so this
is only a note about the intermediate state rather than something that
breaks a previously working configuration.
> - microchip,ksz9477
> - microchip,ksz9897
> - microchip,ksz9896
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260831-ks8995-to-ksz8-v8-0-fd1dbb2b76e8%40kernel.org
next prev parent reply other threads:[~2026-09-02 9:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 20:54 [PATCH net-next v8 0/5] net: dsa: microchip: Add support for KSZ8995XA/KS8995XA Linus Walleij
2026-08-31 20:54 ` [PATCH net-next v8 1/5] net: dsa: microchip: Add fallback Micrel compatibles Linus Walleij
2026-09-02 9:50 ` [net-next,v8,1/5] " netdev-bot+sashiko
2026-08-31 20:54 ` [PATCH net-next v8 2/5] dt-bindings: net: dsa: microchip: Add KSZ8995XA Linus Walleij
2026-09-02 9:50 ` netdev-bot+sashiko [this message]
2026-08-31 20:54 ` [PATCH net-next v8 3/5] net: dsa: tag_ks8995: Add the KS8995 tag handling Linus Walleij
2026-09-02 9:50 ` [net-next,v8,3/5] " netdev-bot+sashiko
2026-08-31 20:54 ` [PATCH net-next v8 4/5] net: dsa: microchip: Support Microchip KSZ8995XA / KS8995XA Linus Walleij
2026-09-02 9:50 ` [net-next,v8,4/5] " netdev-bot+sashiko
2026-08-31 20:54 ` [PATCH net-next v8 5/5] net: dsa: ks8995: Delete surplus driver Linus Walleij
2026-09-02 9:50 ` [net-next,v8,5/5] " 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=178834263728.3394541.8763382902139129360@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.