linux-kernel - Re: [PATCH 0/6] regulator: core: Add support for external outputs

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: <YnIpmdoQTm1gb4fp@hatter.bewilderbeest.net>
Date:   Wed, 4 May 2022 00:22:01 -0700
From:   Zev Weiss <zev@...ilderbeest.net>
To:     Mark Brown <broonie@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>
Cc:     linux-kernel@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        devicetree@...r.kernel.org, openbmc@...ts.ozlabs.org
Subject: Re: [PATCH 0/6] regulator: core: Add support for external outputs

On Tue, May 03, 2022 at 11:50:35PM PDT, Zev Weiss wrote:
>Hello,
>
>This patch series is a new approach at implementing some functionality
>I previously attempted as a separate driver in drivers/misc [0], but I
>think (as suggested by Greg in that thread) ultimately makes more
>sense being built into the regulator subsystem.
>

<snip>

Sorry for the broken threading here (missed a comma in the CC list on 
patch 1 that 'git send-email --dry-run' didn't catch, then forgot to add 
the necessary flags on the second attempt to tack it onto this cover 
letter from the first).

In case it's not obvious, the patches corresponding to this are here: 
https://lore.kernel.org/openbmc/20220504065252.6955-1-zev@bewilderbeest.net/T/


Zev