linux-kernel - 回覆: 回覆: [net] ARM: dts: aspeed: ast2600-evb: Correct phy-mode to rgmii-id

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID:
 <SEYPR06MB5134646C91238EC7336AC3269D32A@SEYPR06MB5134.apcprd06.prod.outlook.com>
Date: Thu, 21 Aug 2025 06:43:33 +0000
From: Jacky Chou <jacky_chou@...eedtech.com>
To: Krzysztof Kozlowski <krzk@...nel.org>, "robh@...nel.org"
	<robh@...nel.org>, "krzk+dt@...nel.org" <krzk+dt@...nel.org>,
	"conor+dt@...nel.org" <conor+dt@...nel.org>, "joel@....id.au"
	<joel@....id.au>, "andrew@...econstruct.com.au"
	<andrew@...econstruct.com.au>, Z-Howard Chiu <howard_chiu@...eedtech.com>,
	"arnd@...db.de" <arnd@...db.de>, "andrew+netdev@...n.ch"
	<andrew+netdev@...n.ch>
CC: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, "linux-aspeed@...ts.ozlabs.org"
	<linux-aspeed@...ts.ozlabs.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>
Subject:
 回覆: 回覆: [net] ARM: dts: aspeed: ast2600-evb: Correct phy-mode to rgmii-id

> >>> According to the latest ethernet-controller.yaml.
> >>> Since there is no RGMII delay on AST2600 EVB, the phy-mode property
> >>> of all MACs change to "rgmii-id" mode.
> >>>
> >>> Fixes: 4d338ee40ba8 ("ARM: dts: aspeed: ast2600-evb: Enable RX delay
> >>> for MAC0/MAC1")
> >>> Fixes: 2ca5646b5c2f ("ARM: dts: aspeed: Add AST2600 and EVB")
> >>> Signed-off-by: Jacky Chou <jacky_chou@...eedtech.com>
> >>> ---
> >>>  arch/arm/boot/dts/aspeed/aspeed-ast2600-evb.dts | 8 ++++----
> >>
> >> No, DTS cannot go to net. Why do you propose that?
> >>
> >
> > If there is a series of patches to add or fix about networking and
> > this series Includes dts or dt-binding, I send it to net or net-next.
> 
> No. That's really irrelevant. And if you change there I2C you send to I2C
> maintainers? That makes no sense.
> 
> You send it to respective maintainers. networking things go to netdev.
> SoC (so DTS) goes to SoC.
> 
> 
> > So, this is just changing the DTS settings, even if it is for MAC,
> > wouldn't it be sent to net?
> 
> You must follow what MAINTAINERS tell you. Don't invent your own rules.
> 

Got it. Thank you.
I will submit this patch again.

Thanks,
Jacky