public inbox for linux-rockchip@lists.infradead.org
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org,
	krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org,
	robh+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
	conor+dt@kernel.org
Subject: Re: [PATCH 0/4] Remove ethernetX aliases from the SoC dtsi for RK3399, RK3368, RK3328 and PX30
Date: Tue, 12 Dec 2023 22:52:38 +0100	[thread overview]
Message-ID: <953de15233be59ae1b3bf69e0d2e7474@manjaro.org> (raw)
In-Reply-To: <170241214697.534713.17361998299651815805.b4-ty@sntech.de>

On 2023-12-12 21:16, Heiko Stuebner wrote:
> On Tue, 12 Dec 2023 08:53:47 +0100, Dragan Simic wrote:
>> Unlike for the I2C buses, GPIO lines and UARTs, the Rockchip SoC TRMs 
>> and
>> datasheets define no numbering for the built-in GMAC(s) or MAC(s), if 
>> there
>> are more than one found in the particular Rockchip SoC.
>> 
>> Moreover, not all boards or devices based on these SoCs actually use 
>> the
>> built-in GMAC(s) or MAC(s).  Thus, let's remove the ethernetX aliases 
>> from
>> the SoC dtsi files and add them back to the appropriate board and 
>> device
>> dts(i) files.  See also [1] for the initial discussion.
>> 
>> [...]
> 
> Applied, thanks!
> 
> [1/4] arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi 
> for RK3399
>       commit: 8030063ca9b019f9dfb90a654f557d8bb15a97a5
> [2/4] arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi 
> for RK3368
>       commit: 7aab60df473c70f74880267500884b12151b160b
> [3/4] arm64: dts: rockchip: Remove ethernetX aliases from the SoC dtsi
> for RK3328
>       commit: 20a9a7667af6b11b7369073d0186d9c92e52db04
> [4/4] arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi 
> for PX30
>       commit: a69907a915e4c15bf7e632cd324ec5c3e38c3afc

Great, thanks!

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

      reply	other threads:[~2023-12-12 21:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12  7:53 [PATCH 0/4] Remove ethernetX aliases from the SoC dtsi for RK3399, RK3368, RK3328 and PX30 Dragan Simic
2023-12-12  7:53 ` [PATCH 1/4] arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi for RK3399 Dragan Simic
2023-12-12  7:53 ` [PATCH 2/4] arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi for RK3368 Dragan Simic
2023-12-12  7:53 ` [PATCH 3/4] arm64: dts: rockchip: Remove ethernetX aliases from the SoC dtsi for RK3328 Dragan Simic
2023-12-12  7:53 ` [PATCH 4/4] arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi for PX30 Dragan Simic
2023-12-12 20:16 ` [PATCH 0/4] Remove ethernetX aliases from the SoC dtsi for RK3399, RK3368, RK3328 and PX30 Heiko Stuebner
2023-12-12 21:52   ` Dragan Simic [this message]

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=953de15233be59ae1b3bf69e0d2e7474@manjaro.org \
    --to=dsimic@manjaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh+dt@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