From: sashiko-bot@kernel.org
To: "Mikhail Lukianchikov" <avermoal@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH] dt-bindings: net: convert microchip,lan78xx.txt to YAML schema
Date: Wed, 08 Jul 2026 16:59:25 +0000 [thread overview]
Message-ID: <20260708165925.9F0D61F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260707165840.107409-1-avermoal@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `ethernet-phy` node schema (which validates `microchip,led-modes`) is incorrectly placed at the root level of the ethernet controller schema instead of within the `mdio` node, causing PHY properties to silently bypass validation.
--
--- Patch [1]: [PATCH] dt-bindings: net: convert microchip,lan78xx.txt to YAML schema ---
commit d20f485d326a6780c198391c5453a7f4df19b905
Author: Mikhail Lukianchikov <avermoal@gmail.com>
dt-bindings: net: convert microchip,lan78xx.txt to YAML schema
Convert the Microchip LAN78xx family (LAN7800, LAN7801, LAN7850) binding
documentation from plain text to DT schema format using YAML.
> diff --git a/Documentation/devicetree/bindings/net/microchip,lan78xx.yaml b/Documentation/devicetree/bindings/net/microchip,lan78xx.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/microchip,lan78xx.yaml
[ ... ]
> + mdio:
> + $ref: /schemas/net/mdio.yaml#
> + unevaluatedProperties: false
> +
> +patternProperties:
> + "^ethernet-phy(@[0-9a-f]+)?$":
[Severity: Medium]
Should this patternProperties block for the ethernet-phy node be nested
inside the mdio property definition rather than at the root level of the
ethernet controller schema?
Because this rule applies to the root level instead of child nodes of mdio,
properties like microchip,led-modes bypass schema validation. Malformed
property values will silently pass dt_binding_check.
> + type: object
> + description: |
> + PHY node for the embedded or external PHY. The PHY address is
> + given by the 'reg' property.
[ ... ]
> + mdio {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + ethernet-phy@1 {
> + reg = <1>;
> + microchip,led-modes = <
[Severity: Medium]
As correctly shown in this example, the ethernet-phy node resides inside
mdio.
Could the schema definition above be updated to match this structure so the
PHY properties are properly evaluated?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260707165840.107409-1-avermoal@gmail.com?part=1
prev parent reply other threads:[~2026-07-08 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 16:58 [PATCH] dt-bindings: net: convert microchip,lan78xx.txt to YAML schema Mikhail Lukianchikov
2026-07-07 18:32 ` Rob Herring (Arm)
2026-07-08 10:56 ` Krzysztof Kozlowski
2026-07-08 16:59 ` sashiko-bot [this message]
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=20260708165925.9F0D61F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=avermoal@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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