From: Conor Dooley <conor@kernel.org>
To: linux-clk@vger.kernel.org, Conor Dooley <conor@kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney@redhat.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-kernel@vger.kernel.org, Waldemar Brodkorb <wbx@openadk.org>
Subject: Re: [PATCH] clk: microchip: rename clk-core to clk-pic32
Date: Tue, 5 May 2026 15:30:31 +0100 [thread overview]
Message-ID: <20260505-imaging-thickness-3b3a8795c870@spud> (raw)
In-Reply-To: <20260225-puzzle-cargo-9d23eedf7957@spud>
From: Conor Dooley <conor.dooley@microchip.com>
On Wed, 25 Feb 2026 17:44:52 +0000, Conor Dooley wrote:
> clk-core is a confusingly generic name, since it is only used by a
> single platform and it uses very similar naming to the "soft" IP cores
> for use in FPGA fabric (CoreClock or similar is what that would be
> called, although nothing like that exists right now) that the FPGA
> business unit produces. Rename it to clk-pic32, matching the prefix
> used by most functions in the driver. As far as I can tell, impact
> on whatever users may (or may not...) exist for the platform is minimal
> as it's built-in only and the functions are called directly from
> clk-pic32mzda.c
>
> [...]
Applied to clk-microchip, thanks!
[1/1] clk: microchip: rename clk-core to clk-pic32
https://git.kernel.org/conor/c/b82e98bf02ca
Thanks,
Conor.
prev parent reply other threads:[~2026-05-05 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 17:44 [PATCH] clk: microchip: rename clk-core to clk-pic32 Conor Dooley
2026-02-25 18:03 ` Brian Masney
2026-05-05 14:30 ` Conor Dooley [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=20260505-imaging-thickness-3b3a8795c870@spud \
--to=conor@kernel.org \
--cc=bmasney@redhat.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor.dooley@microchip.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=wbx@openadk.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