[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c2201037-4f16-4afc-a418-42e4514f27a4@huawei.com>
Date: Fri, 4 Jul 2025 17:07:30 +0800
From: "zhenglifeng (A)" <zhenglifeng1@...wei.com>
To: "Rafael J. Wysocki" <rafael@...nel.org>
CC: <viresh.kumar@...aro.org>, <ionela.voinescu@....com>,
<linux-kernel@...r.kernel.org>, <linux-pm@...r.kernel.org>,
<linuxarm@...wei.com>, <jonathan.cameron@...wei.com>,
<zhanjie9@...ilicon.com>, <lihuisong@...wei.com>, <yubowen8@...wei.com>
Subject: Re: [PATCH 3/7] cpufreq: Contain scaling_cur_freq.attr in
cpufreq_attrs
On 2025/7/3 22:59, Rafael J. Wysocki wrote:
> On Mon, Jun 23, 2025 at 5:30 PM Rafael J. Wysocki <rafael@...nel.org> wrote:
>>
>> On Mon, Jun 23, 2025 at 3:34 PM Lifeng Zheng <zhenglifeng1@...wei.com> wrote:
>>>
>>> After commit c034b02e213d ("cpufreq: expose scaling_cur_freq sysfs file for
>>> set_policy() drivers"), the file scaling_cur_freq is exposed to all
>>> drivers. No need to create this file separately. It's better to be
>>> contained in cpufreq_attrs.
>>
>> Fair enough.
>
> And so applied as 6.17 material along with the [4/7].
>
> The other patches in the series need more work IMV.
>
> Thanks!
Thanks! Then in the next version these two patches won't be sent again.
Powered by blists - more mailing lists