From: "Doug Smythies" <dsmythies@telus.net>
To: "'Rafael J. Wysocki'" <rafael@kernel.org>
Cc: "'LKML'" <linux-kernel@vger.kernel.org>,
"'Srinivas Pandruvada'" <srinivas.pandruvada@linux.intel.com>,
"Doug Smythies" <dsmythies@telus.net>,
"'Linux PM'" <linux-pm@vger.kernel.org>
Subject: RE: [PATCH v3 0/4] cpufreq: intel_pstate: A fix and some cleanups
Date: Mon, 29 Jun 2026 21:21:32 -0700 [thread overview]
Message-ID: <007001dd0847$ee8ab1b0$cba01510$@telus.net> (raw)
In-Reply-To: <4752842.LvFx2qVVIh@rafael.j.wysocki>
Hi Rafael,
On 2026.06.24 10:32 Rafael wrote:
> Hi,
>
> This replaces
>
> https://lore.kernel.org/linux-pm/6005456.DvuYhMxLoT@rafael.j.wysocki/
>
> and drops the most significant change in it which was making intel_pstate
> set cpuinfo_min_freq to a lower value with HWP enabled. That change
> went too far and needs to be reconsidered.
>
> The other changes in the series, and in particular the fix in the first
> patch, are useful and will facilitate further improvements, so here
> they go.
I tested this patch set a little. It seems okay.
... Doug
>
> This series is independent of
>
> https://lore.kernel.org/linux-pm/6286434.lOV4Wx5bFT@rafael.j.wysocki/
>
> and applies to Linux 7.1.
>
> Thanks!
prev parent reply other threads:[~2026-06-30 4:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 17:32 [PATCH v3 0/4] cpufreq: intel_pstate: A fix and some cleanups Rafael J. Wysocki
2026-06-24 17:33 ` [PATCH v3 1/4] cpufreq: intel_pstate: Fix setting minimum P-state at init time Rafael J. Wysocki
2026-06-24 17:34 ` [PATCH v3 2/4] cpufreq: intel_pstate: Introduce intel_pstate_update_freq_limits() Rafael J. Wysocki
2026-06-24 17:35 ` [PATCH v3 3/4] cpufreq: intel_pstate: Consolidate frequency values computation Rafael J. Wysocki
2026-06-24 17:36 ` [PATCH v3 4/4] cpufreq: intel_pstate: Move two functions closer to callers Rafael J. Wysocki
2026-06-30 4:21 ` Doug Smythies [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='007001dd0847$ee8ab1b0$cba01510$@telus.net' \
--to=dsmythies@telus.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@linux.intel.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