linux-kernel - Re: [PATCH RFC 1/2] regulator: introduce regulator monitoring constraints

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] [day] [month] [year] [list]

Message-Id: <20230420145450.1033819-1-bbara93@gmail.com>
Date:   Thu, 20 Apr 2023 16:54:50 +0200
From:   Benjamin Bara <bbara93@...il.com>
To:     broonie@...nel.org
Cc:     DLG-Adam.Ward.opensource@...renesas.com, bbara93@...il.com,
        benjamin.bara@...data.com, lgirdwood@...il.com,
        linux-kernel@...r.kernel.org, mazziesaccount@...il.com,
        support.opensource@...semi.com
Subject: Re: [PATCH RFC 1/2] regulator: introduce regulator monitoring constraints

On Thu, 20 Apr 2023 at 16:37, Mark Brown <broonie@...nel.org> wrote:
> Right, but in any case where the monitoring is enabled then these
> properties would also be needed so there's no point in separately
> configuring it. 
> The driver can supply flags to tell the core to do things like it
> already does for a whole range of other things, there's no need to
> force things to be configured per system in order to factor things
> out. It's just a question of where the core gets information from.

Ah, got it. Thanks for clarification.