Re: [PATCH v2 0/5] regcache: Split out ->populate() and use it

[Mark Brown <broonie@kernel.org>]

On Thu, 30 Oct 2025 18:37:00 +0100, Andy Shevchenko wrote:
> This is a refactoring series to decouple cache initialisation and population.
> On its own it has no functional impact but will be used in the further
> development. Besides that I found this split useful on its own (from the design
> perspective). That's why I decided to send it out as is separately from a bigger
> (and ongoing) work.
> 
> Changelog v2:
> - rebased on top of the recent regcache changes (Mark)
> - a new clean up patch induced by the previous
> 
> [...]

Applied to

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

Thanks!

[1/5] regcache: Add ->populate() callback to separate from ->init()
      commit: 94a3a95f03154d8d4c6206950a7f6ef9a30baec6
[2/5] regcache: rbtree: Split ->populate() from ->init()
      commit: bda6f8749c8e0b10f083dc7a1edf169f349fb776
[3/5] regcache: flat: Remove unneeded check and error message for -ENOMEM
      commit: 27fef3048fe95934f6f2f87341eb33ef6581a075
[4/5] regcache: flat: Split ->populate() from ->init()
      commit: 44c1a444b030647803d900e60f5a8af31a782f0e
[5/5] regcache: maple: Split ->populate() from ->init()
      commit: ed5d499b5c9cc11dd3edae1a7a55db7dfa4f1bdc

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