From: Johan Hovold <johan@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Johan Hovold <johan+linaro@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Rob Herring (Arm)" <robh@kernel.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] cpufreq: fix compile-test defaults
Date: Thu, 17 Apr 2025 08:57:45 +0200 [thread overview]
Message-ID: <aACmabdI0o_TxuNk@hovoldconsulting.com> (raw)
In-Reply-To: <20250417042500.tbuupp3jdpfkk7kh@vireshk-i7>
On Thu, Apr 17, 2025 at 09:55:00AM +0530, Viresh Kumar wrote:
> On 16-04-25, 15:43, Johan Hovold wrote:
> > Commit 3f66425a4fc8 ("cpufreq: Enable COMPILE_TEST on Arm drivers")
> > enabled compile testing of most Arm CPUFreq drivers but left the
> > existing default values unchanged so that many drivers are enabled by
> > default whenever COMPILE_TEST is selected.
> > Fix the default values for drivers that can be compile tested and that
> > should be enabled by default when not compile testing.
> >
> > Fixes: 3f66425a4fc8 ("cpufreq: Enable COMPILE_TEST on Arm drivers")
> I have already applied a similar patch:
>
> https://lore.kernel.org/all/20250404124006.362723-1-krzysztof.kozlowski@linaro.org/
>
> Can you rebase over that please ?
Ah, sorry, I forgot to check linux-next.
Just sent a rebased v2 here:
https://lore.kernel.org/lkml/20250417065535.21358-1-johan+linaro@kernel.org/
Johan
prev parent reply other threads:[~2025-04-17 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 13:43 [PATCH] cpufreq: fix compile-test defaults Johan Hovold
2025-04-17 4:25 ` Viresh Kumar
2025-04-17 6:57 ` Johan Hovold [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=aACmabdI0o_TxuNk@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=johan+linaro@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.