Re: [PATCH] regmap: cache: set max_register with reg_stride

From: Mark Brown
Date: Mon Apr 25 2022 - 10:48:14 EST

On Mon, 25 Apr 2022 20:46:11 +0900, Jeongtae Park wrote:
> Current logic does not consider multi-stride cases,
> the max_register have to calculate with reg_stride
> because it is a kind of address range.

Applied to for-next


[1/1] regmap: cache: set max_register with reg_stride
commit: d640947562cea6158df13fe021b0e117865ba8b3

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.