Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Mikhail Lukianchikov" <avermoal@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v3] dt-bindings: net: microchip,lan78xx: convert to DT schema
Date: Sun, 12 Jul 2026 11:02:56 +0000	[thread overview]
Message-ID: <20260712110257.3111D1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260711105537.11065-2-avermoal@gmail.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The converted DT schema incorrectly rejects a 0-length `microchip,led-modes` property, breaking backward compatibility.
- [Medium] Silently dropping an active maintainer from the MAINTAINERS file without explanation.
--

--- Patch [1]: [PATCH v3] dt-bindings: net: microchip,lan78xx: convert to DT schema ---
commit 2888aafe795bb2f999fce4b5a449417cdf27043b
Author: Mikhail Lukianchikov <avermoal@gmail.com>

dt-bindings: net: microchip,lan78xx: convert to DT schema

Convert the Microchip LAN78xx family (LAN7800, LAN7801, LAN7850) binding
documentation from plain text to DT schema. The conversion adds proper
validation for the 'microchip,led-modes' property inside the MDIO node.

Link: https://lore.kernel.org/netdev/20260709181724.24682-2-avermoal@gmail.com

> diff --git a/Documentation/devicetree/bindings/net/microchip,lan7800.yaml b/Documentation/devicetree/bindings/net/microchip,lan7800.yaml
> new file mode 100644
> index 0000000000000..730999d11e8a0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/microchip,lan7800.yaml
[ ... ]
> +        properties:
> +          microchip,led-modes:
> +            $ref: /schemas/types.yaml#/definitions/uint32-array
> +            minItems: 1

[Severity: Medium]
Does setting minItems to 1 here improperly reject a 0-length property?

The original text binding specified this as a 0..4 element vector. If a device
tree uses an empty property to explicitly disable all LEDs, it will now fail
schema validation.

> +            maxItems: 4
> +            description:
> +              Array of LED mode values for each of up to 4 LEDs.
[ ... ]
> diff --git a/MAINTAINERS b/MAINTAINERS
> index f37a81950e250..157a677a284fc 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -27928,10 +27928,9 @@ F:	drivers/usb/isp1760/*
>  USB LAN78XX ETHERNET DRIVER
>  M:	Thangaraj Samynathan <Thangaraj.S@microchip.com>
>  M:	Rengarajan Sundararajan <Rengarajan.S@microchip.com>
> -M:	UNGLinuxDriver@microchip.com

[Severity: Medium]
This isn't a bug, but was the UNGLinuxDriver@microchip.com maintainer email
intentionally removed?

The commit message doesn't mention dropping this group email, which will no
longer be automatically CC'd on patches to the LAN78XX driver.

>  L:	netdev@vger.kernel.org
>  S:	Maintained

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260711105537.11065-2-avermoal@gmail.com?part=1

      parent reply	other threads:[~2026-07-12 11:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11 10:55 [PATCH v3] dt-bindings: net: microchip,lan78xx: convert to DT schema Mikhail Lukianchikov
2026-07-11 16:58 ` Krzysztof Kozlowski
2026-07-12 11:02 ` 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=20260712110257.3111D1F000E9@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