linux-kernel - Re: [PATCH v1 0/3] cpufreq: drop redundant freq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <180ab822-16d3-4d08-974c-5f8109dc8c82@kylinos.cn>
Date: Tue, 2 Sep 2025 13:54:31 +0800
From: Zihuan Zhang <zhangzihuan@...inos.cn>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: "Rafael J . wysocki" <rafael@...nel.org>,
 zhenglifeng <zhenglifeng1@...wei.com>, linux-pm@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 0/3] cpufreq: drop redundant freq_table argument in
 helpers


在 2025/9/2 13:42, Viresh Kumar 写道:
> On 01-09-25, 19:25, Zihuan Zhang wrote:
>> This patchset updates the cpufreq core and drivers to fully adopt
>> the new policy->freq_table approach introduced in commit
>> e0b3165ba521 ("cpufreq: add 'freq_table' in struct cpufreq_policy").
>>
>> Motivation:
>> - The frequency table is per-policy, not per-CPU, so redundant
>>    freq_table arguments in core helpers and drivers are no longer needed.
>> - Removing the extra argument reduces confusion and potential mistakes.
>>
>> Patch details:
>>
>> 1. cpufreq: core: drop redundant freq_table argument in helpers
>>     - Remove freq_table parameters in core helper functions.
>>     - All helper functions now use policy directly.
>>
>> 2. cpufreq: drivers: remove redundant freq_table argument
>>     - Update cpufreq drivers to match the new core API.
>>     - Calls that previously passed a separate freq_table argument
>>     - No behavior changes, only API consistency.
>>
>> Zihuan Zhang (3):
>>    cpufreq: Drop redundant freq_table parameter
>>    cpufreq: sh: drop redundant freq_table argument
>>    cpufreq: virtual: drop redundant freq_table argument
> Individual patches must not break kernel compilation, but compilation
> breaks after the first patch itself in your series as you have not
> updated all the users.
>
> Merge all three into a single patch.
>
Got it. I wasn’t sure if core and driver changes should be split, but 
yes, merging them into a single patch is better.