Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Chen-Yu Yeh" <chenyou910331@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 2/2] riscv: dts: sophgo: cv180x: Fix internal ephy node name
Date: Sat, 03 Oct 2026 08:51:17 +0000	[thread overview]
Message-ID: <20261003085118.1D0351F0089B@smtp.kernel.org> (raw)
In-Reply-To: <20261003084627.353899-3-chenyou910331@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dts: mismatch between commit message and actual node rename
--

commit ff7773f0965119de993db57ef5ec58df5146e727
Author: Chen-Yu Yeh <chenyou910331@gmail.com>

riscv: dts: sophgo: cv180x: Fix internal ephy node name

This commit updates the internal EPHY node name in cv180x.dtsi to match its
reg property. It aims to rename the node to follow the common ethernet PHY
naming convention.

> diff --git a/arch/riscv/boot/dts/sophgo/cv180x.dtsi b/arch/riscv/boot/dts/sophgo/cv180x.dtsi
> index ec3bf305274ae..cf672cc6b9351 100644
> --- a/arch/riscv/boot/dts/sophgo/cv180x.dtsi
> +++ b/arch/riscv/boot/dts/sophgo/cv180x.dtsi
> @@ -71,7 +71,7 @@ internal_mdio: mdio@0 {
>  				#size-cells = <0>;
>  				reg = <0>;
>  
> -				internal_ephy: phy@0 {
> +				internal_ephy: phy@1 {

[Severity: Medium]
Does this node rename mismatch the commit message and skip generic Ethernet
PHY schema validation?

The commit message states "Rename the node to ethernet-phy@1", but the code
only changes the unit address from "phy@0" to "phy@1", omitting the
"ethernet-" prefix. This mismatch causes the node to silently skip the
standard validation in ethernet-phy.yaml, which expects the node name to
match the pattern ^ethernet-phy(@[a-f0-9]+)?$.

>  					compatible = "ethernet-phy-ieee802.3-c22";
>  					reg = <1>;
>  				};

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

  reply	other threads:[~2026-10-03  8:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03  8:46 [PATCH v2 0/2] riscv: dts: sophgo: Milk-V Duo 256M ethernet support Chen-Yu Yeh
2026-10-03  8:46 ` [PATCH v2 1/2] riscv: dts: sophgo: add Milk-V Duo 256M ethernet support overlay Chen-Yu Yeh
2026-10-03  8:46 ` [PATCH v2 2/2] riscv: dts: sophgo: cv180x: Fix internal ephy node name Chen-Yu Yeh
2026-10-03  8:51   ` sashiko-bot [this message]
2026-10-03  9:25     ` 葉宸佑
2026-10-03 16:23   ` Hiago De Franco
2026-10-03 16:32 ` [PATCH v2 0/2] riscv: dts: sophgo: Milk-V Duo 256M ethernet support Hiago De Franco

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=20261003085118.1D0351F0089B@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=chenyou910331@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