linux-kernel - Re: [PATCH v5 0/7] cpufreq-qcom-hw: Implement full OSM programming

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: <31a1ad25-30f5-8741-fa85-90b93f070f9d@somainline.org>
Date:   Sat, 23 Jan 2021 00:43:18 +0100
From:   AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...ainline.org>
To:     Viresh Kumar <viresh.kumar@...aro.org>
Cc:     bjorn.andersson@...aro.org, agross@...nel.org, rjw@...ysocki.net,
        devicetree@...r.kernel.org, robh+dt@...nel.org,
        amit.kucheria@...aro.org, linux-pm@...r.kernel.org,
        linux-kernel@...r.kernel.org, phone-devel@...r.kernel.org,
        konrad.dybcio@...ainline.org, marijn.suijten@...ainline.org,
        martin.botka@...ainline.org, jeffrey.l.hugo@...il.com
Subject: Re: [PATCH v5 0/7] cpufreq-qcom-hw: Implement full OSM programming

Il 22/01/21 10:46, Viresh Kumar ha scritto:
> On 21-01-21, 20:52, AngeloGioacchino Del Regno wrote:
>>    **
>>    ** NOTE: To "view the full picture", please look at the following
>>    ** patch series:
>>    ** https://patchwork.kernel.org/project/linux-arm-msm/list/?series=413355
>>    **              This is a subset of that series.
>>    **
>>
>> Changes in v5:
>> - Fixed OPP table API abuse, in conjunction with the CPR3 driver
>> - Some minor cleanups
> 
> Tanya had some comments about the driver in the previous version,
> please let such discussions close before sending any new versions. I
> haven't seen any reviews for the major driver changes until this
> version and we are already on V5. Please wait for some time for people
> to review the patches.
> 

Well, okay... it's just that I didn't want reviewers to lose time with
something that had to be fixed, as it wasn't working anymore on the
newest RC, due to a commit that was (rightfully!) blocking the abuse of
the OPP API.

I know that it may be not practical to send a new version while a
discussion is in progress, but this looked like being a critical fix
for the driver that I'm sending.

In any case, this time it is a "final" version and will not get any more
changes unless requested by reviewers/maintainers.

-- Angelo