linux-kernel - Re: [PATCH 0/2] regulator: twl6030: some TWL6032 fixes

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: <166912856621.213500.2092954918480556621.b4-ty@kernel.org>
Date:   Tue, 22 Nov 2022 14:49:26 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-omap@...r.kernel.org, tony@...mide.com, lgirdwood@...il.com,
        linux-kernel@...r.kernel.org, Nicolae_Rosia@...tor.com,
        Andreas Kemnade <andreas@...nade.info>
Subject: Re: [PATCH 0/2] regulator: twl6030: some TWL6032 fixes

On Sun, 20 Nov 2022 23:12:06 +0100, Andreas Kemnade wrote:
> There are some problems regarding TWL6032 regulators, including
> inconsistent states. They come to light during porting support
> for the Epson Moverio BT-200 to newer kernels.
> Information sources are the 3.0 vendor kernel
> (http://epsonservice.goepson.com/downloads/VI-APS/BT200_kernel.tgz)
> and git blame archeology.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: twl6030: re-add TWL6032_SUBCLASS
      commit: 3d6c982b26db94cc21bc9f7784f63e8286b7be62
[2/2] regulator: twl6030: fix get status of twl6032 regulators
      commit: 31a6297b89aabc81b274c093a308a7f5b55081a7

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