linux-kernel - Re: [PATCH 0/5] Convert some regulator drivers to GPIO descriptors

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: <170903349096.16921.1513708498792696039.b4-ty@kernel.org>
Date: Tue, 27 Feb 2024 11:31:30 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Support Opensource <support.opensource@...semi.com>, 
 Lee Jones <lee@...nel.org>, Linus Walleij <linus.walleij@...aro.org>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] Convert some regulator drivers to GPIO descriptors

On Tue, 20 Feb 2024 09:36:23 +0100, Linus Walleij wrote:
> Despite the work to convert the regulator core to GPIO
> descriptors, there are some outliers that use legacy GPIO
> numbers in various ways. Convert them all over.
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/5] regulator: max8973: Finalize switch to GPIO descriptors
      commit: 4d52f575e258c6f93f4180c21afda8634b0d2af5
[2/5] regulator: da9055: Fully convert to GPIO descriptors
      commit: e450a2b3a335332d4a51fe10c9fff8150c6e2364
[3/5] regulator: lp8788-buck: Fully convert to GPIO descriptors
      commit: 95daa868f22b509ad641bf003d9d441d6a2fa505
[4/5] regulator: max8997: Convert to GPIO descriptors
      commit: 84618d5e31cfd01fc3f53a8c2ebb68bc43d8b760
[5/5] regulator: max8998: Convert to GPIO descriptors
      commit: f25828a1eae1ee1a9257e2818b237b8208bd383e

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark