linux-kernel - Re: [PATCH v2 1/2] cpufreq: Reintroduce ready() callback

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]

Date:   Fri, 28 Jan 2022 08:52:08 +0000
From:   Lukasz Luba <lukasz.luba@....com>
To:     Bjorn Andersson <bjorn.andersson@...aro.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Viresh Kumar <viresh.kumar@...aro.org>
Cc:     Jonathan Corbet <corbet@....net>, linux-pm@...r.kernel.org,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v2 1/2] cpufreq: Reintroduce ready() callback

Hi Bjorn,

On 1/28/22 3:25 AM, Bjorn Andersson wrote:
> This effectively revert '4bf8e582119e ("cpufreq: Remove ready()
> callback")' (except the Chinese translation), in order to reintroduce

Is there something wrong with the Chinese translation that it has to be
dropped? Someone has put an effort to create it, I'd assume (and also
based on online translator) that it's correct.

> the ready callback.
> 
> This is needed in order to be able to leave the thermal pressure
> interrupts in the Qualcomm CPUfreq driver disabled during
> initialization, so that it doesn't fire while related_cpus are still 0.

If you are going to push the 2nd patch into stable tree, then you would
also need this one.

Regards,
Lukasz