linux-kernel - Re: 回覆: [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] [thread-next>] [day] [month] [year] [list]

Message-ID: <c288db22-7a80-4dc1-abb5-fb5adb2f5669@kernel.org>
Date: Thu, 21 Aug 2025 08:30:59 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Jacky Chou <jacky_chou@...eedtech.com>, "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: Re: 回覆: [net] ARM: dts: aspeed: ast2600-evb: Correct phy-mode to rgmii-id

On 21/08/2025 08:17, Jacky Chou wrote:
> Hi Krzysztof,
> 
> Thank you for your reply.
> 
>>> 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.

Best regards,
Krzysztof