linux-kernel - Re: [PATCH] regulator: tps65219: Fix is_enabled checking in tps65219_set

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: <166427762040.294303.15716985071433693302.b4-ty@kernel.org>
Date:   Tue, 27 Sep 2022 12:20:20 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Axel Lin <axel.lin@...ics.com>
Cc:     Jerome Neanne <jneanne@...libre.com>, linux-kernel@...r.kernel.org,
        Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [PATCH] regulator: tps65219: Fix is_enabled checking in tps65219_set_bypass

On Mon, 19 Sep 2022 20:23:53 +0800, Axel Lin wrote:
> Testing .enable cannot tell if a regulator is enabled or not, check return
> value of .is_enabled() instead.
> Also remove unneeded ret variable.
> 
> 

Applied to

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

Thanks!

[1/1] regulator: tps65219: Fix is_enabled checking in tps65219_set_bypass
      commit: 947934e389f716d505a656d04388b2ecbe43281d

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