Re: [PATCH v6 0/3] regcache: Avoid accessing non-initialised cache

[Mark Brown]

On Thu, 05 Mar 2026 09:52:59 +0100, Andy Shevchenko wrote:
> Refactor regcache flow that populates cache on initialisation phase
> based on the values in HW. This makes code robust against any possible
> accesses to not-fully initialised caches.
> 
> Changelog v6:
> - refactored to make sure we always clean up the allocated resources (Mark)
> - dropped applied patches
> 
> [...]

Applied to

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

Thanks!

[1/3] regcache: Move count check and cache_bypass assignment to the caller
      commit: 8e2d279724944f788edc633e4888107eae666a37
[2/3] regcache: Allocate and free reg_defaults on the same level
      commit: 0cb7ae981894ff1fd0283813a17253250a747cf5
[3/3] regcache: Move HW readback after cache initialisation
      commit: e7662bced2e98ffa2c572126677deb9cf55d43b3

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