From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] arm: dts: renesas: Drop _clk suffix from clock node names
Date: Wed, 5 Apr 2017 14:17:55 -0400 [thread overview]
Message-ID: <20170405181755.GA31226@verge.net.au> (raw)
In-Reply-To: <CAMuHMdWSLKjcyQP25mPCwn8EV1xzAyC=AipT8E0DbeVoEeemAw@mail.gmail.com>
On Wed, Apr 05, 2017 at 09:09:20AM +0200, Geert Uytterhoeven wrote:
> Hi Stephen,
>
> On Wed, Apr 5, 2017 at 3:38 AM, Stephen Boyd <sboyd@codeaurora.org> wrote:
> > On 04/03, Geert Uytterhoeven wrote:
> >> The current practice is to not add _clk suffixes to clock node names in
> >> DT, as these names are used as the actual clock names.
> >>
> >> This patch removes the remaining offenders in the various Renesas DTSes.
> >
> > This changes the names in the clk framework too though? If you're
> > ok with that I'm ok too.
>
> Yes, that's my main motivation doing this: it's a bit silly to have some clocks
> show up in /sys/kernel/debug/clk/clk_summary with a "_clk" suffix.
>
> > Acked-by: Stephen Boyd <sboyd@codeaurora.org>
>
> Thanks!
Thanks, I have queued these up.
prev parent reply other threads:[~2017-04-05 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 10:08 [PATCH 0/3] arm: dts: renesas: Drop _clk suffix from clock node names Geert Uytterhoeven
2017-04-03 10:08 ` [PATCH 1/3] ARM: dts: r8a7790: Drop _clk suffix from external CAN clock node name Geert Uytterhoeven
2017-04-03 10:08 ` [PATCH 2/3] ARM: dts: r8a7791: " Geert Uytterhoeven
2017-04-03 10:08 ` [PATCH 3/3] arm64: dts: r8a7795: salvator-x: Drop _clk suffix from X12 " Geert Uytterhoeven
2017-04-05 1:38 ` [PATCH 0/3] arm: dts: renesas: Drop _clk suffix from clock node names Stephen Boyd
2017-04-05 7:09 ` Geert Uytterhoeven
2017-04-05 18:17 ` Simon Horman [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=20170405181755.GA31226@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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).