linux-kernel - Re: (subset) [PATCH 0/3] regulator: rtq2208: Fix incorrect code section

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: <174222789497.223336.16672496286681303116.b4-ty@kernel.org>
Date: Mon, 17 Mar 2025 16:11:34 +0000
From: Mark Brown <broonie@...nel.org>
To: Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, cy_huang@...htek.com
Cc: Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>, 
 linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: (subset) [PATCH 0/3] regulator: rtq2208: Fix incorrect code
 section

On Mon, 17 Mar 2025 18:06:20 +0800, cy_huang@...htek.com wrote:
> This patch series is to fix
> - buck converter phase mapping
> - Correctly get LDO DVS capability
> 
> ChiYuan Huang (3):
>   regulator: rtq2208: Fix incorrect buck converter phase mapping
>   regulator: rtq2208: Fix the LDO DVS capability
>   regulator: dt-bindings: rtq2208: Remove unnecessary property of fixed
>     LDO VOUT
> 
> [...]

Applied to

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

Thanks!

[1/3] regulator: rtq2208: Fix incorrect buck converter phase mapping
      commit: 1742e7e978babb0f548f85c4c6bcfebe13b88722
[2/3] regulator: rtq2208: Fix the LDO DVS capability
      commit: b65439d9015024c37c6b8a17c0569ec44675a979

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