linux-kernel - Re: [PATCH 1/6] regulator: mcp16502: Add supplier for regulators

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: <6c1a1bf6-fb9a-4dda-9777-6749fe333d03@microchip.com>
Date: Wed, 7 Aug 2024 07:35:52 +0000
From: <Andrei.Simion@...rochip.com>
To: <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/6] regulator: mcp16502: Add supplier for regulators

On 02.08.2024 20:58, Mark Brown wrote:
>> In regulator.yaml exists .*-supply [1] which practically allows every
>> char sequence before -supply. In the binding microchip,mcp16502.yaml [2]
>> each node under the regulators includes all the rules/documentation
>> from regulator.yaml , so I supposed that it is unnecessary to add
>> in the binding of those new property.
>> What is your opinion? Let me know any thoughts.
> The specific names for a given device are supposed to be specified,
> there's a bunch of existing bindings that appear to do that.

Ok, I will sent V2 with binding update.

Best Regards,
Andrei Simion