linux-kernel - Re: [PATCH] regulator: tps65219: use generic 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: <167544620617.1020619.12568195566452835847.b4-ty@kernel.org>
Date:   Fri, 03 Feb 2023 17:43:26 +0000
From:   Mark Brown <broonie@...nel.org>
To:     tony@...mide.com, lgirdwood@...il.com,
        Jerome Neanne <jneanne@...libre.com>
Cc:     linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
        khilman@...libre.com, nm@...com, msp@...libre.com
Subject: Re: [PATCH] regulator: tps65219: use generic set_bypass()

On Fri, 03 Feb 2023 15:01:19 +0100, Jerome Neanne wrote:
> Due to wrong interpretation of the specification,
> custom implementation was used instead of standard regmap helper.
> LINK: https://lore.kernel.org/all/c2014039-f1e8-6976-33d6-52e2dd4e7b66@baylibre.com/
> 
> Fixes: c12ac5fc3e0a ("regulator: drivers: Add TI TPS65219 PMIC regulators support")
> 
> Regulator does NOT require to be off to be switched to bypass mode.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: tps65219: use generic set_bypass()
      commit: 0365df81145a4cfaae5f4da896160de512256e6d

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