linux-kernel - Re: (subset) [PATCH v3 0/2] regulator: fix race with probing of dummy 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <174188300085.450690.13914957191633099426.b4-ty@kernel.org>
Date: Thu, 13 Mar 2025 16:23:20 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Douglas Anderson <dianders@...omium.org>, 
 Christian Eggers <ceggers@...i.de>
Cc: linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH v3 0/2] regulator: fix race with probing of
 dummy regulator

On Thu, 13 Mar 2025 11:27:37 +0100, Christian Eggers wrote:
> These two patches are already in linux-next. I made a minor adjustment
> proposed by Doug. Can they still be updated?
> 

Applied to

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

Thanks!

[2/2] regulator: check that dummy regulator has been probed before using it
      commit: 2c7a50bec4958f1d1c84d19cde518d0e96a676fd

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