From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Lukas Bulwahn <lbulwahn@redhat.com>
Cc: Brian Masney <bmasney@redhat.com>,
linux-mips@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] clk: microchip: fix typo in reference to a config option
Date: Thu, 5 Feb 2026 10:05:07 +0100 [thread overview]
Message-ID: <aYRdQxCHhHxMhdPY@alpha.franken.de> (raw)
In-Reply-To: <20260203090101.348879-1-lukas.bulwahn@redhat.com>
On Tue, Feb 03, 2026 at 10:01:01AM +0100, Lukas Bulwahn wrote:
> From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
>
> Commit 026d70dcfe5d ("clk: microchip: core: allow driver to be compiled
> with COMPILE_TEST") introduces a typo when referring to a config option in
> an ifdef directive.
>
> Fix this typo.
>
> Fixes: 026d70dcfe5d ("clk: microchip: core: allow driver to be compiled with COMPILE_TEST")
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>
> ---
> drivers/clk/microchip/clk-core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clk/microchip/clk-core.c b/drivers/clk/microchip/clk-core.c
> index 509cdc060c34..b764ca059e68 100644
> --- a/drivers/clk/microchip/clk-core.c
> +++ b/drivers/clk/microchip/clk-core.c
> @@ -74,7 +74,7 @@
> /* SoC specific clock needed during SPLL clock rate switch */
> static struct clk_hw *pic32_sclk_hw;
>
> -#ifdef CONFIG_MATCH_PIC32
> +#ifdef CONFIG_MACH_PIC32
> /* add instruction pipeline delay while CPU clock is in-transition. */
> #define cpu_nop5() \
> do { \
> --
> 2.52.0
applied to mips-next
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2026-02-05 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 9:01 [PATCH] clk: microchip: fix typo in reference to a config option Lukas Bulwahn
2026-02-03 17:54 ` Brian Masney
2026-02-05 9:05 ` Thomas Bogendoerfer [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=aYRdQxCHhHxMhdPY@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=bmasney@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lbulwahn@redhat.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@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