linux-kernel - Re: [PATCH 0/2] Add Richtek RT8092 support

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: <176640324016.139369.9597811188220020982.b4-ty@kernel.org>
Date: Mon, 22 Dec 2025 11:34:00 +0000
From: Mark Brown <broonie@...nel.org>
To: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, cy_huang@...htek.com
Cc: Liam Girdwood <lgirdwood@...il.com>, Alan Lan <alan_lan@...htek.com>, 
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Add Richtek RT8092 support

On Fri, 19 Dec 2025 14:36:18 +0800, cy_huang@...htek.com wrote:
> This patch series add rt8092 regulator support.
> 
> ChiYuan Huang (2):
>   dt-bindings: regulator: rt5739: Add compatible for rt8092
>   regulator: Add rt8092 support
> 
>  .../bindings/regulator/richtek,rt5739.yaml    |   5 +
>  drivers/regulator/Kconfig                     |   9 +
>  drivers/regulator/Makefile                    |   1 +
>  drivers/regulator/rt8092.c                    | 313 ++++++++++++++++++
>  4 files changed, 328 insertions(+)
>  create mode 100644 drivers/regulator/rt8092.c
> 
> [...]

Applied to

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

Thanks!

[1/2] dt-bindings: regulator: rt5739: Add compatible for rt8092
      commit: e5eb5638d632cf1180454acf16391ea9450e6295
[2/2] regulator: Add rt8092 support
      commit: 32a708ba5db50cf928a1f1b2039ceef33de2c286

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