linux-kernel - Re: [PATCH] regulator: Documentation fix for regulator error notification helper

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: <162971664758.27145.14089229701843613260.b4-ty@kernel.org>
Date:   Mon, 23 Aug 2021 12:06:12 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Matti Vaittinen <mazziesaccount@...il.com>,
        Matti Vaittinen <matti.vaittinen@...rohmeurope.com>
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
        Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [PATCH] regulator: Documentation fix for regulator error notification helper

On Mon, 23 Aug 2021 10:56:51 +0300, Matti Vaittinen wrote:
> The helper to send IRQ notification for regulator errors had still
> old description mentioning calling BUG() as a last resort when
> error status reading has kept failing for more times than a given
> threshold.
> 
> The impementation calling BUG() did never end-up in-tree but was
> replaced by hopefully more sophisticated handler trying to power-off
> the system.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: Documentation fix for regulator error notification helper
      commit: ad3ead1efe057029bf112e13d7ef5901915d6abd

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