linux-kernel - Re: [PATCH v2 0/8] regulator: core: allow regulator

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: <176822826163.92368.16808418574188317303.b4-ty@kernel.org>
Date: Mon, 12 Jan 2026 14:31:01 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Javier Martinez Canillas <javier@....samsung.com>, 
 Jon Hunter <jonathanh@...dia.com>, Dmitry Baryshkov <lumag@...nel.org>, 
 Oleksij Rempel <o.rempel@...gutronix.de>, 
 André Draszik <andre.draszik@...aro.org>
Cc: Peter Griffin <peter.griffin@...aro.org>, 
 Tudor Ambarus <tudor.ambarus@...aro.org>, 
 Will McVicker <willmcvicker@...gle.com>, Juan Yescas <jyescas@...gle.com>, 
 kernel-team@...roid.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/8] regulator: core: allow regulator_register()
 with missing required supply

On Fri, 09 Jan 2026 08:38:36 +0000, André Draszik wrote:
> With these attached patches it becomes possible again to support
> hardware designs with multiple PMICs where individual rails of each act
> as required supplies for rails of the other (due to the latter being
> e.g. always-on), and vice-versa.
> 
> Google Pixel 6 and 6 Pro (oriole and raven) are examples of such
> designs.
> 
> [...]

Applied to

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

Thanks!

[1/8] regulator: core: update two debug messages
      commit: 96e7a88d32de2554a5d7e54e87eb03d445dd6924
[2/8] regulator: core: fix locking in regulator_resolve_supply() error path
      commit: 497330b203d2c59c5ff3fa4c34d14494d7203bc3
[3/8] regulator: core: move supply check earlier in set_machine_constraints()
      commit: 86a8eeb0e913f4b6a55dabba5122098d4e805e55
[4/8] regulator: core: streamline supply resolution for always-on/boot-on regulators
      commit: 4f3323b752bfcc185c98ce4fb841cca8b700a7c0
[5/8] regulator: core: remove dead code in regulator_resolve_supply()
      commit: bdbdc4b398254597c9b6ac279f336750996bc0a6
[6/8] regulator: core: don't ignore errors from event forwarding setup
      commit: e23c0a59dabae9166bbea26fc05d08e7d9e900b7
[7/8] regulator: core: reresolve unresolved supplies when available
      commit: 304f5784e97281f18ef4bed574cbe5fcf6ce2f2e
[8/8] regulator: core: don't fail regulator_register() with missing required supply
      commit: 8d38423d9dea7353a8a54a3ab2e0d0aa04ed34d0

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