We had some bugs in the past with the high bit set, add some coverage
for this to ensure it doesn't creep in.

Signed-off-by: Mark Brown <broonie@kernel.org>
---
Mark Brown (2):
      regmap: Allow a base register to be specified for the RAM regmap
      regmap: Test rbtree and maple caches for very high register numbers

 drivers/base/regmap/internal.h       |  1 +
 drivers/base/regmap/regmap-kunit.c   | 98 ++++++++++++++++++++++++++++++++++--
 drivers/base/regmap/regmap-ram.c     | 26 +++++++---
 drivers/base/regmap/regmap-raw-ram.c | 21 +++++---
 4 files changed, 129 insertions(+), 17 deletions(-)
---
base-commit: 23688febe4b44b10f4b454eb1cde0ba379a84119
change-id: 20260815-regmap-kunit-cache-high-bit-ddf03045f4a8

Best regards,
--  
Mark Brown <broonie@kernel.org>

On Tue, 18 Aug 2026 22:50:43 +0100, Mark Brown wrote:
> regmap: Test caches for regmaps with high bits set in register numbers
> 
> We had some bugs in the past with the high bit set, add some coverage
> for this to ensure it doesn't creep in.

Applied to

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

Thanks!

[1/2] regmap: Allow a base register to be specified for the RAM regmap
      https://git.kernel.org/broonie/regmap/c/a99aacfb67df
[2/2] regmap: Test rbtree and maple caches for very high register numbers
      https://git.kernel.org/broonie/regmap/c/b26da6db3da9

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