From: "zhenglifeng (A)" <zhenglifeng1@huawei.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: <rafael@kernel.org>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>,
<jonathan.cameron@huawei.com>, <zhanjie9@hisilicon.com>,
<lihuisong@huawei.com>, <fanghao11@huawei.com>
Subject: Re: [PATCH v2 4/4] cpufreq: ACPI: Remove set_boost in acpi_cpufreq_cpu_init()
Date: Fri, 24 Jan 2025 17:11:37 +0800 [thread overview]
Message-ID: <e9f4d2ac-6561-406b-b370-500ab52ff110@huawei.com> (raw)
In-Reply-To: <20250124085959.r3cf7qfd7fxz2iiw@vireshk-i7>
On 2025/1/24 16:59, Viresh Kumar wrote:
> On 21-01-25, 11:44, Viresh Kumar wrote:
>> There are more cleanups in drivers that can be done though. I will try
>> that once this series is merged.
>
> https://lore.kernel.org/751338633b070ee570c3c7da053bd6b9497ee50e.1737707712.git.viresh.kumar@linaro.org
>
Nice!
next prev parent reply other threads:[~2025-01-24 9:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 10:14 [PATCH v2 0/4] cpufreq: Fix some boost errors related to CPU online and offline Lifeng Zheng
2025-01-17 10:14 ` [PATCH v2 1/4] cpufreq: Fix re-boost issue after hotplugging a cpu Lifeng Zheng
2025-01-20 8:27 ` Viresh Kumar
2025-01-20 9:10 ` zhenglifeng (A)
2025-01-20 9:21 ` Viresh Kumar
2025-01-20 9:21 ` Viresh Kumar
2025-01-17 10:14 ` [PATCH v2 2/4] cpufreq: Introduce a more generic way to set default per-policy boost flag Lifeng Zheng
2025-01-20 9:01 ` Viresh Kumar
2025-01-21 1:45 ` zhenglifeng (A)
2025-01-21 4:20 ` Viresh Kumar
2025-01-21 6:22 ` zhenglifeng (A)
2025-01-21 6:37 ` Viresh Kumar
2025-02-04 16:41 ` Aboorva Devarajan
2025-02-05 5:01 ` Viresh Kumar
2025-02-05 18:22 ` Aboorva Devarajan
2025-01-17 10:14 ` [PATCH v2 3/4] cpufreq: CPPC: Fix wrong max_freq in policy initialization Lifeng Zheng
2025-01-20 9:28 ` Viresh Kumar
2025-01-17 10:14 ` [PATCH v2 4/4] cpufreq: ACPI: Remove set_boost in acpi_cpufreq_cpu_init() Lifeng Zheng
2025-01-21 6:14 ` Viresh Kumar
2025-01-24 8:59 ` Viresh Kumar
2025-01-24 9:11 ` zhenglifeng (A) [this message]
2025-04-15 10:29 ` Viresh Kumar
2025-01-21 6:38 ` [PATCH v2 0/4] cpufreq: Fix some boost errors related to CPU online and offline Viresh Kumar
2025-01-23 20:07 ` 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=e9f4d2ac-6561-406b-b370-500ab52ff110@huawei.com \
--to=zhenglifeng1@huawei.com \
--cc=fanghao11@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=lihuisong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=zhanjie9@hisilicon.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