linux-kernel - Re: [PATCH v3 0/2] 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: <174231003498.125964.14980151487641276196.b4-ty@kernel.org>
Date: Tue, 18 Mar 2025 15:00: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: Rob Herring <robh@...nel.org>, linux-kernel@...r.kernel.org, 
 devicetree@...r.kernel.org
Subject: Re: [PATCH v3 0/2] regulator: rtq2208: Fix incorrect code section

On Tue, 18 Mar 2025 19:07:03 +0800, cy_huang@...htek.com wrote:
> The old v1 series are here for the reference
> https://lore.kernel.org/lkml/cover.1742204502.git.cy_huang@richtek.com/
> 
> Since the subset of v1 patch series are accepted, there's only one
> document change are left and still need to be reviewed.
> 
> ChiYuan Huang (2):
>   regulator: dt-bindings: rtq2208: Mark fixed LDO VOUT property as
>     deprecated
>   regulator: dt-bindings: rtq2208: Cleanup whitespace
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: dt-bindings: rtq2208: Mark fixed LDO VOUT property as deprecated
      commit: 64b3fb38b45f7f36954801c45d9b7c19d82d6f83
[2/2] regulator: dt-bindings: rtq2208: Cleanup whitespace
      commit: 5e9491370a58bee1784999aa42f48f1f7289f641

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