(subset) [PATCH v8 00/14] mfd/pinctrl/regulator: Add RK806 Support

[Mark Brown]

On Thu, 04 May 2023 19:36:04 +0200, Sebastian Reichel wrote:
> All existing boards using RK3588/RK3588s use RK806 PMICs. This series is now
> the main blocker for full upstream support of those boards and it would be good
> to have it merged for 6.5 :) The patches have been tested on multiple different
> platforms and are mainly missing an Ack from Mark or Liam for the rk808-regulator
> changes.
> 
> Merging must happen through a single tree, since the pinctrl and regulator
> drivers rely on the register definitions from the include file added by the MFD
> patch. My suggested merge strategy is that Lee creates an immutable branch for
> the regulator/pinctrl tree once all Acks have been collected.
> 
> [...]

Applied to

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

Thanks!

[10/14] regulator: expose regulator_find_closest_bigger
        commit: 431cb97b763133fba8b1c68c1ed089315f25e4dd
[11/14] regulator: rk808: fix asynchronous probing
        commit: 1b9e86d445a0f5c6d8dcbaf11508cb5dfb5848a8
[12/14] regulator: rk808: cleanup parent device usage
        commit: 5111c931f36cebe77d4ce66964c348e6eb4afca0
[13/14] regulator: rk808: revert to synchronous probing
        commit: 22a94021e7d2b456c6abb59ad0a7ce4e94933d4a
[14/14] regulator: rk808: add rk806 support
        commit: f991a220a44726c54c2332569a2a80bf074aa775

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