From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: 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 1/2] arm: dts: arm: Drop redundant fixed-factor clocks
Date: Thu, 27 Jun 2024 22:26:39 +0200 [thread overview]
Message-ID: <CACRpkdaCMfpa25Ap3NyeWgiTTsiWJZD5Ui3YPdDB8p05OE_Lxg@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqKAXnu=CDsOAOoxF0sBnzMxaCDVUU4Z+2k8kseTMvc+eA@mail.gmail.com>
On Thu, Jun 27, 2024 at 9:06 PM Rob Herring <robh@kernel.org> wrote:
> On Wed, May 29, 2024 at 2:47 AM Linus Walleij <linus.walleij@linaro.org> wrote:
> > On Tue, May 28, 2024 at 9:15 PM Rob Herring (Arm) <robh@kernel.org> wrote:
> >
> > > There's not much reason to have multiple fixed-factor-clock instances
> > > which are all the same factor and clock input. Drop the nodes, but keep
> > > the labels to minimize the changes and keep some distinction of the
> > > different clocks.
> > >
> > > Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> >
> > Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> Someone going to pick this up?
I put patch 1/2 into the SoC patchwork:
https://patchwork.kernel.org/project/linux-soc/patch/20240627-arm-dts-fixes-v1-1-40a2cb7d344b@linaro.org/
I think Sudeep probably want to pick up patch 2/2 so as to avoid
conflicts.
Yours,
Linus Walleij
prev parent reply other threads:[~2024-06-27 20:26 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
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 [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=CACRpkdaCMfpa25Ap3NyeWgiTTsiWJZD5Ui3YPdDB8p05OE_Lxg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.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 \
--cc=sudeep.holla@arm.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).