On Sat, 10 Jun 2023 14:57:46 +0100, Mark Brown wrote:
Many of the Realtek I2C/SPI devices only support single register read and write operations so don't benefit from using the rbtree cache instead of the more modern maple tree cache, convert them to maple tree.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[01/16] ASoC: rt1011: Use maple tree register cache (no commit info) [02/16] ASoC: rt1019: Use maple tree register cache (no commit info) [03/16] ASoC: rt1305: Use maple tree register cache (no commit info) [04/16] ASoC: rt1308: Use maple tree register cache commit: 4f69e29ace9dce5f8226bfc99b77b8497d3d3d79 [05/16] ASoC: rt5514: Use maple tree register cache (no commit info) [06/16] ASoC: rt5616: Use maple tree register cache (no commit info) [07/16] ASoC: rt5631: Use maple tree register cache (no commit info) [08/16] ASoC: rt5640: Use maple tree register cache (no commit info) [09/16] ASoC: rt5645: Use maple tree register cache (no commit info) [10/16] ASoC: rt5651: Use maple tree register cache (no commit info) [11/16] ASoC: rt5660: Use maple tree register cache (no commit info) [12/16] ASoC: rt5665: Use maple tree register cache (no commit info) [13/16] ASoC: rt5665: Use maple tree register cache (no commit info) [14/16] ASoC: rt5668: Use maple tree register cache (no commit info) [15/16] ASoC: rt5670: Use maple tree register cache (no commit info) [16/16] ASoC: rt5682: Use maple tree register cache (no commit info)
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