linux-kernel - Re: [PATCH v1] regulator: core: Convert warning to debug print

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: <df9cffef-ef00-4e52-9df1-8bed3605a014@linux.ibm.com>
Date:   Mon, 16 Oct 2023 07:24:59 -0500
From:   Ninad Palsule <ninad@...ux.ibm.com>
To:     Mark Brown <broonie@...nel.org>
Cc:     joel@....id.au, eajames@...ux.ibm.com, lgirdwood@...il.com,
        linux-kernel@...r.kernel.org, lakshmiy@...ibm.com
Subject: Re: [PATCH v1] regulator: core: Convert warning to debug print

Hello Mark,

On 10/13/23 10:38, Mark Brown wrote:
> On Thu, Oct 12, 2023 at 04:45:48PM -0500, Ninad Palsule wrote:
>
>> You are right there are regulators for these supplies but they are managed
>> by the
>> hardware hence not added in the device tree. I checked dts/aspeed directory
>> and
>> non of the machine has “vcc-supply” defined and lot of them use eeprom.
> Fixed voltage regulators can be used for this.
ok, So far we don't need it.
>
>> Also, I thought that this message is only useful in the lab to indicate
>> developer
>> whether they missed the device tree definition or not but its not useful in
>> the
>> field.  Hence proposed to put it under DEBUG.
> The theory is that it shouldn't come up in the field since people see it
> during development and fix things then, are people actually looking at
> these logs?  I think my understanding was that they're mostly BMCs
> people interacted with via a UI of some kind.

During testing people look at this logs. We will ignore this warning for 
now.

Thanks!

~Ninad