Re: (subset) [PATCH v2 00/10] regmap: clean up and improve __regmap_init()
From: Mark Brown
Date: Thu Nov 19 2026 - 15:22:09 EST
On Fri, 13 Nov 2026 23:31:48 +0800, Peng Fan wrote:
> regmap: clean up and improve __regmap_init()
>
> This series includes three fixes for pre-existing regmap issues noticed
> during review, improves the __regmap_init() error handling and removes the
> last user of regmap_bus::free_on_exit. Patches 1-3 are fixes suitable for stable;
> patches 4-9 are cleanups with no functional change intended; patch 10 adds
> KUnit coverage for the new bus callback.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-7.5
Thanks!
[02/10] regmap-i2c: keep bus raw write limit when applying read quirk
https://git.kernel.org/broonie/regmap/c/931deb7a04b7
[03/10] regmap-i2c: fix write limit clamping for adapter quirks
https://git.kernel.org/broonie/regmap/c/94da81cb6fdc
[04/10] regmap: deduplicate fast_io checks
https://git.kernel.org/broonie/regmap/c/edcc17880bf5
[05/10] regmap: factor out regmap_set_lock()
https://git.kernel.org/broonie/regmap/c/25203a86e6c3
[06/10] regmap: factor out regmap_init_ranges()
https://git.kernel.org/broonie/regmap/c/37ccd50b8376
[07/10] regmap: factor out format initialisation into helpers
https://git.kernel.org/broonie/regmap/c/7ba85f2e9681
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