Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@oss.qualcomm.com>
Cc: robh@kernel.org, wsa+renesas@sang-engineering.com,
	dri-devel@lists.freedesktop.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH net-next] dt-bindings: net: Use consistent indentation in the example
Date: Mon, 14 Sep 2026 12:31:05 +0000	[thread overview]
Message-ID: <20260914123106.44CC81F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260913122910.99457-3-krzysztof.kozlowski@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The `mdio0` block containing the `phy0` and `phy1` node definitions was accidentally deleted during indentation cleanup, resulting in unresolved phandle references.
--

commit 3067fd6538b78515dc2a63a2028de505854e6496
Author: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

dt-bindings: net: Use consistent indentation in the example

This patch corrects the indentation in various device tree binding examples
to conform to a consistent 2- or 4-space indent style. It aims to resolve
dt-check-style warnings across multiple net and wireless bindings files.

> diff --git a/Documentation/devicetree/bindings/net/cortina,gemini-ethernet.yaml b/Documentation/devicetree/bindings/net/cortina,gemini-ethernet.yaml
> index f0b5bea2458d5..da9bc170cd543 100644
> --- a/Documentation/devicetree/bindings/net/cortina,gemini-ethernet.yaml
> +++ b/Documentation/devicetree/bindings/net/cortina,gemini-ethernet.yaml
> @@ -87,18 +87,6 @@ examples:
>      #include <dt-bindings/interrupt-controller/irq.h>
>      #include <dt-bindings/clock/cortina,gemini-clock.h>
>      #include <dt-bindings/reset/cortina,gemini-reset.h>
> -    mdio0: mdio {
> -      #address-cells = <1>;
> -      #size-cells = <0>;
> -      phy0: ethernet-phy@1 {
> -        reg = <1>;
> -        device_type = "ethernet-phy";
> -      };
> -      phy1: ethernet-phy@3 {
> -        reg = <3>;
> -        device_type = "ethernet-phy";
> -      };
> -    };

[Severity: Low]
Does the removal of this mdio0 block break the device tree example
compilation?

Since phy-handle = <&phy0>; and phy-handle = <&phy1>; are still used later
in the gmac0 and gmac1 nodes, deleting these target nodes results in
unresolved phandles when running make dt_binding_check.

Was this block accidentally dropped during the indentation cleanup?

>  
>      ethernet@60000000 {
>          compatible = "cortina,gemini-ethernet";
> @@ -110,28 +98,28 @@ examples:
>          ranges;
>  
>          gmac0: ethernet-port@0 {
> -                compatible = "cortina,gemini-ethernet-port";
> -                reg = <0x60008000 0x2000>, /* Port 0 DMA/TOE */
> -                      <0x6000a000 0x2000>; /* Port 0 GMAC */
> -                interrupt-parent = <&intcon>;
> -                interrupts = <1 IRQ_TYPE_LEVEL_HIGH>;
> -                resets = <&syscon GEMINI_RESET_GMAC0>;
> -                clocks = <&syscon GEMINI_CLK_GATE_GMAC0>;
> -                clock-names = "PCLK";
> -                phy-mode = "rgmii";
> -                phy-handle = <&phy0>;
> +            compatible = "cortina,gemini-ethernet-port";
> +            reg = <0x60008000 0x2000>, /* Port 0 DMA/TOE */
> +                  <0x6000a000 0x2000>; /* Port 0 GMAC */
> +            interrupt-parent = <&intcon>;
> +            interrupts = <1 IRQ_TYPE_LEVEL_HIGH>;
> +            resets = <&syscon GEMINI_RESET_GMAC0>;
> +            clocks = <&syscon GEMINI_CLK_GATE_GMAC0>;
> +            clock-names = "PCLK";
> +            phy-mode = "rgmii";
> +            phy-handle = <&phy0>;
>          };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260913122910.99457-3-krzysztof.kozlowski@oss.qualcomm.com?part=1

  parent reply	other threads:[~2026-09-14 12:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-13 12:29 [PATCH net-next] dt-bindings: net: Use consistent indentation in the example Krzysztof Kozlowski
2026-09-14  9:14 ` Claudiu Manoil
2026-09-14  9:17   ` Krzysztof Kozlowski
2026-09-14 12:31 ` sashiko-bot [this message]
2026-09-14 15:50   ` Krzysztof Kozlowski
2026-09-14 12:50 ` netdev-bot+sashiko
2026-09-14 15:52   ` Krzysztof Kozlowski

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=20260914123106.44CC81F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=wsa+renesas@sang-engineering.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox