From: Pierre Gondois <pierre.gondois@arm.com>
To: Lifeng Zheng <zhenglifeng1@huawei.com>,
rafael@kernel.org, viresh.kumar@linaro.org,
robert.moore@intel.com, lenb@kernel.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, acpica-devel@lists.linux.dev,
linuxarm@huawei.com, jonathan.cameron@huawei.com,
zhanjie9@hisilicon.com, lihuisong@huawei.com,
cenxinghai@h-partners.com, yubowen8@huawei.com
Subject: Re: [PATCH 0/3] cpufreq: CPPC: Some optimizations for cppc_cpufreq.c.
Date: Wed, 28 May 2025 15:26:14 +0200 [thread overview]
Message-ID: <237e957e-82fa-41ea-9f6e-bd37f51003aa@arm.com> (raw)
In-Reply-To: <20250526113057.3086513-1-zhenglifeng1@huawei.com>
Reviewed-by: Pierre Gondois <pierre.gondois@arm.com>
On 5/26/25 13:30, Lifeng Zheng wrote:
> This patch series makes some minor optimizations for cppc_cpufreq.c to
> makes codes cleaner.
>
> Lifeng Zheng (3):
> cpufreq: CPPC: Remove cpu_data_list
> cpufreq: CPPC: Return void in populate_efficiency_class()
> cpufreq: CPPC: Remove forward declaration of
> cppc_cpufreq_register_em()
>
> drivers/cpufreq/cppc_cpufreq.c | 59 +++++++++-------------------------
> include/acpi/cppc_acpi.h | 1 -
> 2 files changed, 15 insertions(+), 45 deletions(-)
>
next prev parent reply other threads:[~2025-05-28 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 11:30 [PATCH 0/3] cpufreq: CPPC: Some optimizations for cppc_cpufreq.c Lifeng Zheng
2025-05-26 11:30 ` [PATCH 1/3] cpufreq: CPPC: Remove cpu_data_list Lifeng Zheng
2025-05-26 11:30 ` [PATCH 2/3] cpufreq: CPPC: Return void in populate_efficiency_class() Lifeng Zheng
2025-05-26 11:30 ` [PATCH 3/3] cpufreq: CPPC: Remove forward declaration of cppc_cpufreq_register_em() Lifeng Zheng
2025-05-28 13:26 ` Pierre Gondois [this message]
2025-05-29 6:28 ` [PATCH 0/3] cpufreq: CPPC: Some optimizations for cppc_cpufreq.c zhenglifeng (A)
2025-06-17 2:33 ` zhenglifeng (A)
2025-06-18 19:06 ` Rafael J. Wysocki
2025-06-19 5:47 ` Viresh Kumar
2025-06-19 5:46 ` Viresh Kumar
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=237e957e-82fa-41ea-9f6e-bd37f51003aa@arm.com \
--to=pierre.gondois@arm.com \
--cc=acpica-devel@lists.linux.dev \
--cc=cenxinghai@h-partners.com \
--cc=jonathan.cameron@huawei.com \
--cc=lenb@kernel.org \
--cc=lihuisong@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=viresh.kumar@linaro.org \
--cc=yubowen8@huawei.com \
--cc=zhanjie9@hisilicon.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox