linux-kernel - Re: [PATCH] regulator: bd718x7: Clarify comment by moving it

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: <174965660569.52384.4243364071140563212.b4-ty@kernel.org>
Date: Wed, 11 Jun 2025 16:43:25 +0100
From: Mark Brown <broonie@...nel.org>
To: Matti Vaittinen <mazziesaccount@...il.com>, 
 Matti Vaittinen <mazziesaccount@...il.com>
Cc: Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: bd718x7: Clarify comment by moving it

On Tue, 10 Jun 2025 08:32:06 +0300, Matti Vaittinen wrote:
> The BD718x7 needs to disable voltage monitoring for a duration of
> certain voltage changes.
> 
> The comment explaining use of msleep(1) instead of a more accurate
> delay(), was placed to a function which disabled the protection. The
> actual sleeping is done in a different place of the code, after the
> voltage has been changed.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: bd718x7: Clarify comment by moving it
      commit: 55d9fd9819de09e70401b3b5262ff46d5de951b7

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