| Message ID | 20240320085740.4604-1-liubo03@inspur.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | regulator: convert to use maple tree register cache | expand |
On Wed, 20 Mar 2024 04:57:27 -0400, Bo Liu wrote: > The maple tree register cache is based on a much more modern data structure > than the rbtree cache and makes optimisation choices which are probably > more appropriate for modern systems than those made by the rbtree cache. > > Bo Liu (13): > regulator: da9121: convert to use maple tree register cache > regulator: da9211: convert to use maple tree register cache > regulator: isl9305: convert to use maple tree register cache > regulator: max8973: convert to use maple tree register cache > regulator: mt6311: convert to use maple tree register cache > regulator: pca9450: convert to use maple tree register cache > regulator: pf8x00: convert to use maple tree register cache > regulator: pfuze100: convert to use maple tree register cache > regulator: rtmv20: convert to use maple tree register cache > regulator: rtq6752: convert to use maple tree register cache > regulator: tps51632: convert to use maple tree register cache > regulator: tps62360: convert to use maple tree register cache > regulator: rpi-panel-attiny: convert to use maple tree register cache > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [01/13] regulator: da9121: convert to use maple tree register cache commit: d92eb7c333c5ac8d8add10d5a211ac9c405e4393 [02/13] regulator: da9211: convert to use maple tree register cache commit: 03ddbcbe2f1ca9fac2759849be6714d8e82aa331 [03/13] regulator: isl9305: convert to use maple tree register cache commit: 66a4ead5ed9393d250105fcbe6e3525e1cdd977a [04/13] regulator: max8973: convert to use maple tree register cache commit: 36649db5b216a85cfd7937a289c4cdd0b4b69126 [05/13] regulator: mt6311: convert to use maple tree register cache commit: bc125125125c10ec14764d153227c95ad0fd0b48 [06/13] regulator: pca9450: convert to use maple tree register cache commit: 0b03e9cb8b137490f4adedf07482384ffeee7145 [07/13] regulator: pf8x00: convert to use maple tree register cache commit: cea065dced280306ff5a4f7adfeb3773c49b2818 [08/13] regulator: pfuze100: convert to use maple tree register cache commit: 0332f074f5c3d8c2a32db24c9dcc3c3f13056cef [09/13] regulator: rtmv20: convert to use maple tree register cache commit: 43edba6b670bc4f5426e77873b400fe91f8d3c75 [10/13] regulator: rtq6752: convert to use maple tree register cache commit: 81c180e77d60755ca5ff217786e2f427ccab04e0 [11/13] regulator: tps51632: convert to use maple tree register cache commit: 9500d38e50d0cfd33536454a204dedb9d47d84a3 [12/13] regulator: tps62360: convert to use maple tree register cache commit: fe258f54c0a85c1bfc0e836e20c3e4e52f1a8318 [13/13] regulator: rpi-panel-attiny: convert to use maple tree register cache commit: ab470abe58c09b2fbe2c1478e67a904fd803e84f 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