Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Arthur Crepin Leblond" <arthur@marmottus.net>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v7 1/3] dt-bindings: net: wiznet,w5100: convert to DT schema
Date: Sat, 05 Sep 2026 12:36:28 +0000	[thread overview]
Message-ID: <20260905123628.AF03E1F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260904-wiznet-link-gpio-v7-1-69f01b70c96f@marmottus.net>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Mismatch between v5 changelog claim and actual implementation regarding the `interrupts` property.
--

commit 71f148f5cb00ff21bcdd03a6c89a26a42be35836
Author: Arthur Crepin Leblond <arthur@marmottus.net>

dt-bindings: net: wiznet,w5100: convert to DT schema

This commit converts the Wiznet w5x00 SPI Ethernet controller binding from
plain text to DT schema.

> ---
> v6:
>  - Put back the reviewed by tag from Krzysztof Kozlowski from v4
> 
> v5:
>  - Remove gpio/gpio.h include from DT example
>  - Make the DT interrupts property dynamic from the compatible one
>  - Fix DT bindings errors

[ ... ]

> diff --git a/Documentation/devicetree/bindings/net/wiznet,w5100.yaml b/Documentation/devicetree/bindings/net/wiznet,w5100.yaml
> new file mode 100644
> index 0000000000000..601d828bae927
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/wiznet,w5100.yaml

[ ... ]

> +  spi-max-frequency:
> +    description:
> +      According to the w5500 datasheet, the chip allows a maximum of 80 MHz,
> +      however, board designs may need to limit this value.
> +    maximum: 80000000
> +
> +required:
> +  - compatible
> +  - reg
> +  - interrupts

[Severity: Low]
The v5 changelog notes mention making the interrupts property dynamic based on
the compatible string, but it remains unconditionally required here in the
global required block.

Is the changelog description out of date, or was the dynamic property logic
unintentionally dropped from the schema during a rebase?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260904-wiznet-link-gpio-v7-0-69f01b70c96f@marmottus.net?part=1

  reply	other threads:[~2026-09-05 12:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 12:35 [PATCH net-next v7 0/3] w5100: restore GPIO-based link detection Arthur Crepin Leblond
2026-09-04 12:35 ` [PATCH net-next v7 1/3] dt-bindings: net: wiznet,w5100: convert to DT schema Arthur Crepin Leblond
2026-09-05 12:36   ` sashiko-bot [this message]
2026-09-09 12:38   ` netdev-bot+sashiko
2026-09-11 15:30     ` Arthur Crepin Leblond
2026-09-04 12:35 ` [PATCH net-next v7 2/3] dt-bindings: net: wiznet,w5100: add link status interrupt Arthur Crepin Leblond
2026-09-09 12:39   ` netdev-bot+sashiko
2026-09-11 15:33     ` Arthur Crepin Leblond
2026-09-11 15:56       ` Arthur Crepin Leblond
2026-09-04 12:36 ` [PATCH net-next v7 3/3] w5100: detect carrier state using link status bit and optional interrupt Arthur Crepin Leblond
2026-09-05 12:36   ` sashiko-bot
2026-09-11 15:40     ` Arthur Crepin Leblond
2026-09-09 12:39   ` netdev-bot+sashiko
2026-09-10 11:27     ` Paolo Abeni
2026-09-10 12:28       ` Arthur Crepin Leblond

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=20260905123628.AF03E1F00A3D@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=arthur@marmottus.net \
    --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