devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Rob Herring (Arm)" <robh@kernel.org>,
	soc@kernel.org,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
	Richard Cochran <richardcochran@gmail.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] arm64: dts: amd/seattle: Fix bus, mmc, and ethernet node names
Date: Fri, 7 Mar 2025 16:53:08 +0100	[thread overview]
Message-ID: <10c65b97-a57a-48fb-b843-bf556e46466f@kernel.org> (raw)
In-Reply-To: <20250306-dt-amd-fixes-v1-3-011c423ba99a@kernel.org>

On 07/03/2025 02:07, Rob Herring (Arm) wrote:
> Use preferred node names for bus, mmc, and ethernet.
> 
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> ---
>  arch/arm64/boot/dts/amd/amd-overdrive-rev-b0.dts | 2 +-
>  arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi     | 2 +-
>  arch/arm64/boot/dts/amd/amd-seattle-xgbe-b.dtsi  | 4 ++--
>  3 files changed, 4 insertions(+), 4 deletions(-)
> 


Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Best regards,
Krzysztof


  reply	other threads:[~2025-03-07 15:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07  1:07 [PATCH 0/4] arm64: dts: AMD Seattle clean-ups Rob Herring (Arm)
2025-03-07  1:07 ` [PATCH 1/4] arm64: dts: amd/seattle: Base Overdrive B1 on top of B0 version Rob Herring (Arm)
2025-03-07 15:54   ` Krzysztof Kozlowski
2025-03-07  1:07 ` [PATCH 2/4] arm64: dts: amd/seattle: Move and simplify fixed clocks Rob Herring (Arm)
2025-03-07 15:52   ` Krzysztof Kozlowski
2025-03-07  1:07 ` [PATCH 3/4] arm64: dts: amd/seattle: Fix bus, mmc, and ethernet node names Rob Herring (Arm)
2025-03-07 15:53   ` Krzysztof Kozlowski [this message]
2025-03-07  1:07 ` [PATCH 4/4] arm64: dts: amd/seattle: Drop undocumented "spi-controller" properties Rob Herring (Arm)
2025-03-07 15:51   ` Krzysztof Kozlowski

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=10c65b97-a57a-48fb-b843-bf556e46466f@kernel.org \
    --to=krzk@kernel.org \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=robh@kernel.org \
    --cc=soc@kernel.org \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=thomas.lendacky@amd.com \
    /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).