linux-kernel - Re: [PATCH v3 0/2] regulator: Add TPS65185

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: <176830946479.57532.9044166740752095483.b4-ty@kernel.org>
Date: Tue, 13 Jan 2026 13:04:24 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, Guenter Roeck <linux@...ck-us.net>, 
 Andreas Kemnade <andreas@...nade.info>
Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org, 
 linux-hwmon@...r.kernel.org, 
 Krzysztof Kozlowski <krzysztof.kozlowski@....qualcomm.com>, 
 Josua Mayer <josua.mayer@....eu>
Subject: Re: [PATCH v3 0/2] regulator: Add TPS65185

On Fri, 02 Jan 2026 11:13:55 +0100, Andreas Kemnade wrote:
> Add a driver for the TPS65185 regulator which provides the
> comparatively high voltages needed for electronic paper displays.
> 
> Datasheet for the TPS65185 is at https://www.ti.com/lit/gpn/tps65185
> 
> To simplify things, include the hwmon part directly which is only
> one temperature sensor and there are no other functions besides regulators
> in this chip.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: dt-bindings: Document TI TPS65185
      commit: da1456e435ae84852bda484cd4d60f47228d52fc
[2/2] regulator: Add TPS65185 driver
      commit: b0fc1e7701940d12ea2c41f386aa552bc4cc3629

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