linux-kernel - Re: [PATCH] regulator (max5970): Fix regulator child node name

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: <7a687805-3c99-4e1e-bad7-f40ed06ea96e@sirena.org.uk>
Date: Tue, 13 Feb 2024 15:37:45 +0000
From: Mark Brown <broonie@...nel.org>
To: Naresh Solanki <naresh.solanki@...ements.com>
Cc: Liam Girdwood <lgirdwood@...il.com>, mazziesaccount@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator (max5970): Fix regulator child node name

On Tue, Feb 13, 2024 at 08:28:00PM +0530, Naresh Solanki wrote:
> Update regulator child node name to lower case i.e., sw0 & sw1 as
> descibed in max5970 dt binding.

Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)