[PATCH 0/3] regulator: pf9453: optimize PMIC PF9453 driver

Joy Zou posted 3 patches 3 months, 1 week ago
drivers/regulator/pf9453-regulator.c | 22 +---------------------
1 file changed, 1 insertion(+), 21 deletions(-)
[PATCH 0/3] regulator: pf9453: optimize PMIC PF9453 driver
Posted by Joy Zou 3 months, 1 week ago
For the details, please check the patch commit log.

Signed-off-by: Joy Zou <joy.zou@nxp.com>
---
Joy Zou (3):
      regulator: pf9453: change the device ID register address
      regulator: pf9453: remove low power mode
      regulator: pf9453: remove unused I2C_LT register

 drivers/regulator/pf9453-regulator.c | 22 +---------------------
 1 file changed, 1 insertion(+), 21 deletions(-)
---
base-commit: 98bd8b16ae57e8f25c95d496fcde3dfdd8223d41
change-id: 20251103-b4-next-pf9453-c9f8fb6e0c10

Best regards,
-- 
Joy Zou <joy.zou@nxp.com>
Re: [PATCH 0/3] regulator: pf9453: optimize PMIC PF9453 driver
Posted by Mark Brown 3 months ago
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