linux-kernel - Re: [PATCH 0/3] regulator: pf9453: optimize PMIC PF9453 driver

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: <176226876897.2228237.4299470805943237670.b4-ty@kernel.org>
Date: Tue, 04 Nov 2025 15:06:08 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Frank Li <Frank.Li@....com>, 
 Joy Zou <joy.zou@....com>
Cc: linux-kernel@...r.kernel.org, imx@...ts.linux.dev
Subject: Re: [PATCH 0/3] regulator: pf9453: optimize PMIC PF9453 driver

On Mon, 03 Nov 2025 11:26:46 +0800, Joy Zou wrote:
> For the details, please check the patch commit log.
> 
> 

Applied to

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

Thanks!

[1/3] regulator: pf9453: change the device ID register address
      commit: a2d4691b3fec6a2360e4ec953d06819ea055c3e7
[2/3] regulator: pf9453: remove low power mode
      commit: 0144a2b29d95af8523c308116de65d398d6e935b
[3/3] regulator: pf9453: remove unused I2C_LT register
      commit: 2ecc8c089802e033d2e5204d21a9f467e2517df9

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