Re: [PATCH RFC v3 0/4] regmap: convert map->lock/unlock users to a scoped guard

[Mark Brown]

On Thu, 24 Sep 2026 14:30:51 +0800, Peng Fan (OSS) wrote:
> regmap: convert map->lock/unlock users to a scoped guard
> 
> The regmap lock is taken by calling the lock and unlock callbacks
> directly at every call site:
> 
> 	map->lock(map->lock_arg);
> 	...
> 	map->unlock(map->lock_arg);
> 
> [...]

Applied to

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

Thanks!

[1/4] regmap: convert lock/unlock to a scoped guard
      https://git.kernel.org/broonie/regmap/c/80328b41ea28
[2/4] regcache: use the regmap scoped lock guard
      https://git.kernel.org/broonie/regmap/c/23f1120dcbea
[3/4] regcache: rbtree: use the regmap scoped lock guard
      https://git.kernel.org/broonie/regmap/c/555a1bd78bbc
[4/4] regmap: debugfs: use the regmap scoped lock guard
      https://git.kernel.org/broonie/regmap/c/9999d5a07ee0

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