From: Sudeep Holla <sudeep.holla@arm.com>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liviu Dudau <liviu.dudau@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm/arm64: dts: arm: Use generic clock and regulator nodenames
Date: Sun, 2 Jun 2024 17:00:20 +0100 [thread overview]
Message-ID: <20240602160020.azbf7pytiu57vwo5@bogus> (raw)
In-Reply-To: <20240528191536.1444649-2-robh@kernel.org>
On Tue, May 28, 2024 at 02:15:32PM -0500, Rob Herring (Arm) wrote:
> With the recent defining of preferred naming for fixed clock and
> regulator nodes, convert the Arm Ltd. boards to use the preferred
> names. In the cases which had a unit-address, warnings about missing
> "reg" property are fixed.
>
Thanks for the cleanup.
Do you want to take it through DT tree or prefer me to take it. I think
I have one another patch from Krzysztof for Juno DTS IIRC.
I am fine either way. In case you take it:
Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-06-02 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 19:15 [PATCH 1/2] arm: dts: arm: Drop redundant fixed-factor clocks Rob Herring (Arm)
2024-05-28 19:15 ` [PATCH 2/2] arm/arm64: dts: arm: Use generic clock and regulator nodenames Rob Herring (Arm)
2024-05-29 8:47 ` Linus Walleij
2024-06-02 16:00 ` Sudeep Holla [this message]
2024-06-28 14:32 ` Rob Herring
2024-07-29 20:30 ` Guenter Roeck
2024-07-30 20:45 ` Rob Herring
2024-05-29 8:46 ` [PATCH 1/2] arm: dts: arm: Drop redundant fixed-factor clocks Linus Walleij
2024-06-27 19:05 ` Rob Herring
2024-06-27 20:26 ` Linus Walleij
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=20240602160020.azbf7pytiu57vwo5@bogus \
--to=sudeep.holla@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lpieralisi@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