linux-kernel - Re: [PATCH] regulator: fixed: Rely on the core freeing the enable GPIO

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: <176495056668.27605.14199249889679769517.b4-ty@kernel.org>
Date: Fri, 05 Dec 2025 16:02:46 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Diederik de Haas <diederik@...ow-tech.com>, Mark Brown <broonie@...nel.org>
Cc: Haotian Zhang <vulab@...as.ac.cn>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: fixed: Rely on the core freeing the enable
 GPIO

On Thu, 04 Dec 2025 19:39:34 +0000, Mark Brown wrote:
> In order to simplify ownership rules for enable GPIOs supplied by drivers
> regulator_register() always takes ownership of them, even if it ends up
> failing for some other reason. We therefore should	not free the GPIO if
> registration fails but just let the core worry about things.
> 
> 

Applied to

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

Thanks!

[1/1] regulator: fixed: Rely on the core freeing the enable GPIO
      commit: 79a45ddcdbba330f5139c7c7ff7042d69cf147b2

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