linux-kernel - Re: [PATCH v7 00/29] Rework the trip points creation

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:   Mon, 3 Oct 2022 08:41:28 +0100
From:   Lukasz Luba <lukasz.luba@....com>
To:     "Rafael J. Wysocki" <rafael@...nel.org>,
        Daniel Lezcano <daniel.lezcano@...aro.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux PM <linux-pm@...r.kernel.org>,
        "Zhang, Rui" <rui.zhang@...el.com>,
        Raju Rangoju <rajur@...lsio.com>,
        Amit Kucheria <amitk@...nel.org>,
        Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
        Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Alim Akhtar <alim.akhtar@...sung.com>,
        Thierry Reding <thierry.reding@...il.com>,
        Keerthy <j-keerthy@...com>,
        Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v7 00/29] Rework the trip points creation

Hi Rafael and Daniel,

[I had to remove some CC entries due to internal limits]

On 9/30/22 18:39, Rafael J. Wysocki wrote:
> On Thu, Sep 29, 2022 at 9:35 PM Rafael J. Wysocki <rafael@...nel.org> wrote:
>>
>> On Thu, Sep 29, 2022 at 4:57 PM Daniel Lezcano
>> <daniel.lezcano@...aro.org> wrote:
>>>
>>> On 29/09/2022 15:58, Rafael J. Wysocki wrote:
>>>> On Thu, Sep 29, 2022 at 2:26 PM Daniel Lezcano
>>>> <daniel.lezcano@...aro.org> wrote:
>>>>>
>>>>>
>>>>> Hi Rafael,
>>>>>
>>>>> are you happy with the changes?
>>>>
>>>> I'll have a look and let you know.
>>>
>>> Great, thanks
>>
>> Well, because you have not added the history of changes to the
>> patches, that will take more time than it would otherwise.
> 
> Done.  I've sent ACKs and still had a comment on one patch (minor but
> still).  When that is addressed, the four initial core patches should
> be good to go in.
> 
> I'm trusting you regarding the thermal/of changes (even though I think
> that it would be good if someone involved in that code could review
> them) and if you are confident about all of the driver changes, they
> are fine with me too.

Sorry for being late. I have been busy with some internal bug hunting.
I'll review the code today and test it on my dev boards. Although,
I have only ~4 different platforms so would cover a slice of this patch
set. The core changes should be covered.

Regards,
Lukasz