From: Pierre Gondois <pierre.gondois@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-kernel@vger.kernel.org,
Lifeng Zheng <zhenglifeng1@huawei.com>,
Huang Rui <ray.huang@amd.com>,
"Gautham R. Shenoy" <gautham.shenoy@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Perry Yuan <perry.yuan@amd.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v8 0/2] cpufreq: Introduce boost frequency QoS
Date: Fri, 27 Mar 2026 17:07:58 +0100 [thread overview]
Message-ID: <d13a7a60-dcee-483e-8ea8-a551ca2db467@arm.com> (raw)
In-Reply-To: <mv7ham5nlret74v6kvstourb2f7d4zxurbgpqm57w7c3hzdw2c@w2rx5r2t5vyg>
On 3/27/26 04:43, Viresh Kumar wrote:
> On 26-03-26, 21:43, Pierre Gondois wrote:
>> Pierre Gondois (2):
>> cpufreq: Remove max_freq_req update for pre-existing policy
>> cpufreq: Add boost_freq_req QoS request
>>
>> drivers/cpufreq/amd-pstate.c | 2 --
>> drivers/cpufreq/cppc_cpufreq.c | 10 ++-----
>> drivers/cpufreq/cpufreq.c | 50 +++++++++++++++++++++-------------
>> include/linux/cpufreq.h | 1 +
>> 4 files changed, 34 insertions(+), 29 deletions(-)
> Thanks Pierre for your patience.
Thanks for the review (to Lifeng aswell)
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>
next prev parent reply other threads:[~2026-03-27 16:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 20:43 [PATCH v8 0/2] cpufreq: Introduce boost frequency QoS Pierre Gondois
2026-03-26 20:44 ` [PATCH v8 1/2] cpufreq: Remove max_freq_req update for pre-existing policy Pierre Gondois
2026-03-26 20:44 ` [PATCH v8 2/2] cpufreq: Add boost_freq_req QoS request Pierre Gondois
2026-03-29 9:00 ` Zhongqiu Han
2026-03-30 2:10 ` zhenglifeng (A)
2026-03-30 4:00 ` Zhongqiu Han
2026-03-30 7:16 ` zhenglifeng (A)
2026-03-30 13:01 ` Zhongqiu Han
2026-03-30 5:20 ` Viresh Kumar
2026-03-30 12:55 ` Zhongqiu Han
2026-03-31 3:14 ` Zhongqiu Han
2026-03-31 3:58 ` Viresh Kumar
2026-03-27 3:43 ` [PATCH v8 0/2] cpufreq: Introduce boost frequency QoS Viresh Kumar
2026-03-27 16:07 ` Pierre Gondois [this message]
2026-03-30 19:58 ` Rafael J. Wysocki
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=d13a7a60-dcee-483e-8ea8-a551ca2db467@arm.com \
--to=pierre.gondois@arm.com \
--cc=gautham.shenoy@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perry.yuan@amd.com \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=viresh.kumar@linaro.org \
--cc=zhenglifeng1@huawei.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 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.