linux-kernel - Re: [PATCH] regulator: core: fix false positive in regulator_late

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: <164433287788.2964991.4272324071658669274.b4-ty@kernel.org>
Date:   Tue, 08 Feb 2022 15:07:57 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Oliver Barta <o.barta89@...il.com>, linux-kernel@...r.kernel.org
Cc:     Pi-Hsun Shih <pihsun@...omium.org>,
        Rolf Evers-Fischer <Rolf.Evers.Fischer@...iv.com>,
        Oliver Barta <oliver.barta@...iv.com>,
        Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [PATCH] regulator: core: fix false positive in regulator_late_cleanup()

On Tue, 8 Feb 2022 09:46:45 +0100, Oliver Barta wrote:
> From: Oliver Barta <oliver.barta@...iv.com>
> 
> The check done by regulator_late_cleanup() to detect whether a regulator
> is on was inconsistent with the check done by _regulator_is_enabled().
> While _regulator_is_enabled() takes the enable GPIO into account,
> regulator_late_cleanup() was not doing that.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: core: fix false positive in regulator_late_cleanup()
      commit: 4e2a354e3775870ca823f1fb29bbbffbe11059a6

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