On Mon, 09 Sep 2024 15:51:11 +0200, Krzysztof Kozlowski wrote: > Few cleanups (safer code), built tested. Last two patches should > probably be tested. > > Best regards, > Krzysztof > Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [01/17] regulator: da9052: Constify static data commit: 9653007e7d878609be205ced4803ca57be341845 [02/17] regulator: da9055: Constify static data commit: dfa9e708c63e7833c61f551069d3ff4b03af7895 [03/17] regulator: da9063: Constify static data commit: 0601c1e5c4a1162c909675233645889237b003a2 [04/17] regulator: da9121: Constify static data commit: b3f1e8e32ef579907fe0c0c9c102bb13883454d6 [05/17] regulator: da9211: Constify static data (no commit info) [06/17] regulator: hi6421: Constify static data commit: b94afa51cad448d7d9bcb600ce267153132369ad [07/17] regulator: hi6421v600: Constify static data commit: 5ec424afc95ab2490ae28b3e7756e6e9b271a5f0 [08/17] regulator: tps65023: Constify static data commit: 7fb636dc26d6fc532fbc96fc74847afedc128154 [09/17] regulator: max77826: Drop unused 'rdesc' in 'struct max77826_regulator_info' commit: 653976707d03f9c8e07f1c7733f27c89a1d5eb1c [10/17] regulator: max77826: Constify static data commit: 96d7ee7cb01203ae0b6078631738754424d89cf8 [11/17] regulator: mtk-dvfsrc: Constify static data commit: 90b94a05b6cd54b6ae65d09df86d7b602a228ae1 [12/17] regulator: pcap: Constify static data commit: 7f1bfca46b1524a774d03eccd8042935c453843a [13/17] regulator: pfuze100: Constify static data commit: 6f4fd2b8a5c08656d293ed491335747ff3d34104 [14/17] regulator: qcom-refgen: Constify static data commit: 7eb5d065ec6725d7da9a4f7ba71b6ff4aaf7eb42 [15/17] regulator: hi6421v530: Drop unused 'eco_microamp' commit: e9c7ff34c26d009c2f7c3d51236ed5a808dbc0d7 [16/17] regulator: hi6421v530: Use container_of and constify static data commit: 7dd36b3287182bc889953f7741bdcef037109210 [17/17] regulator: max77650: Use container_of and constify static data commit: c4d6a804713ac080841d1711a98ae1a6ecaede38 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
