devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jacky Chou <jacky_chou@aspeedtech.com>,
	"robh@kernel.org" <robh@kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"joel@jms.id.au" <joel@jms.id.au>,
	"andrew@codeconstruct.com.au" <andrew@codeconstruct.com.au>,
	Z-Howard Chiu <howard_chiu@aspeedtech.com>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 回覆: [net] ARM: dts: aspeed: ast2600-evb: Correct phy-mode to rgmii-id
Date: Thu, 21 Aug 2025 08:30:59 +0200	[thread overview]
Message-ID: <c288db22-7a80-4dc1-abb5-fb5adb2f5669@kernel.org> (raw)
In-Reply-To: <SEYPR06MB5134106F024EB9EC32472A329D32A@SEYPR06MB5134.apcprd06.prod.outlook.com>

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@aspeedtech.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

  reply	other threads:[~2025-08-21  6:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21  5:25 [net] ARM: dts: aspeed: ast2600-evb: Correct phy-mode to rgmii-id Jacky Chou
2025-08-21  6:09 ` Krzysztof Kozlowski
2025-08-21  6:17   ` 回覆: " Jacky Chou
2025-08-21  6:30     ` Krzysztof Kozlowski [this message]
2025-08-21  6:43       ` 回覆: " Jacky Chou
2025-08-22  0:11 ` Andrew Lunn

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=c288db22-7a80-4dc1-abb5-fb5adb2f5669@kernel.org \
    --to=krzk@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@codeconstruct.com.au \
    --cc=arnd@arndb.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=howard_chiu@aspeedtech.com \
    --cc=jacky_chou@aspeedtech.com \
    --cc=joel@jms.id.au \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).