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 v10 1/4] dt-bindings: net: dsa: microchip: Add KSZ8995XA
Date: Wed, 09 Sep 2026 09:39:25 +0000 [thread overview]
Message-ID: <20260909093926.34F8D1F00AC4@smtp.kernel.org> (raw)
In-Reply-To: <20260908-ks8995-to-ksz8-v10-1-7379239eb65f@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The newly added compatible string 'microchip,ksz8995xa' (a 5-port switch) is incorrectly added to an exclusion list meant for 3-port switches, bypassing generic DSA port validation.
--
commit 2397d2b8fd3c47150c21e2d07ecb537ee6972ff6
Author: Linus Walleij <linusw@kernel.org>
dt-bindings: net: dsa: microchip: Add KSZ8995XA
This commit adds a new compatible string for the KSZ8995XA 5-port switch. It
updates the main properties list and an if-then conditional block in the
device tree binding schema.
> diff --git a/Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml b/Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml
> index 8d4a3a9a33fcc..ed39530b6cbbb 100644
> --- a/Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml
> +++ b/Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml
[ ... ]
> @@ -122,6 +123,7 @@ allOf:
> enum:
> - microchip,ksz8863
> - microchip,ksz8873
> + - microchip,ksz8995xa
[Severity: Low]
Does adding this 5-port switch to this specific enum block bypass generic
DSA port validation?
Since this list routes these specific compatible strings to the 'else' branch
which enforces a 3-port maximum limit, adding the KSZ8995XA here appears to
apply 3-port validation rules to a 5-port switch.
This could lead to incomplete schema evaluation for ports 3 and 4, either
allowing invalid configurations to silently pass or causing valid
configurations to fail validation when running dt_binding_check.
> then:
> $ref: dsa.yaml#/$defs/ethernet-ports
> else:
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260908-ks8995-to-ksz8-v10-0-7379239eb65f@kernel.org?part=1
next prev parent reply other threads:[~2026-09-09 9:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 9:38 [PATCH net-next v10 0/4] net: dsa: microchip: Add support for KSZ8995XA/KS8995XA Linus Walleij
2026-09-08 9:38 ` [PATCH net-next v10 1/4] dt-bindings: net: dsa: microchip: Add KSZ8995XA Linus Walleij
2026-09-09 9:39 ` sashiko-bot [this message]
2026-09-09 10:29 ` Linus Walleij
2026-09-09 12:39 ` netdev-bot+sashiko
2026-09-08 9:38 ` [PATCH net-next v10 2/4] net: dsa: tag_ks8995: Add the KS8995 tag handling Linus Walleij
2026-09-09 9:39 ` sashiko-bot
2026-09-09 10:47 ` Linus Walleij
2026-09-09 12:39 ` netdev-bot+sashiko
2026-09-08 9:38 ` [PATCH net-next v10 3/4] net: dsa: microchip: Support Microchip KSZ8995XA / KS8995XA Linus Walleij
2026-09-09 9:39 ` sashiko-bot
2026-09-09 10:51 ` Linus Walleij
2026-09-09 12:39 ` netdev-bot+sashiko
2026-09-08 9:38 ` [PATCH net-next v10 4/4] net: dsa: ks8995: Delete surplus driver Linus Walleij
2026-09-09 12:39 ` 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=20260909093926.34F8D1F00AC4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox