linux-kernel - Re: [PATCH 1/2] regulator: rtq2208: Correct buck group2 phase mapping logic

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: <176427979987.171723.1183612758277430342.b4-ty@kernel.org>
Date: Thu, 27 Nov 2025 21:43:19 +0000
From: Mark Brown <broonie@...nel.org>
To: cy_huang@...htek.com
Cc: Liam Girdwood <lgirdwood@...il.com>, 
 Edward Kim <edward_kim@...htek.com>, linux-kernel@...r.kernel.org, 
 stable@...r.kernel.org, Yoon Dong Min <dm.youn@...echips.com>
Subject: Re: [PATCH 1/2] regulator: rtq2208: Correct buck group2 phase
 mapping logic

On Thu, 27 Nov 2025 10:25:50 +0800, cy_huang@...htek.com wrote:
> Correct buck group2 H and F mapping logic.
> 
> 

Applied to

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

Thanks!

[1/2] regulator: rtq2208: Correct buck group2 phase mapping logic
      commit: 45cc214152bc1f6b1cc135532cd7cdbe08716aaf
[2/2] regulator: rtq2208: Correct LDO2 logic judgment bits
      commit: 8684229e19c4185d53d6fb7004d733907c865a91

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