On Sat, 26 Sep 2020 14:55:42 +0200, kholk11@xxxxxxxxx wrote: > This patch series enables support for the regulators as found in > the PM660 and PM660L PMICs. > While at it, and to make them work, along with other regulators > for other qcom PMICs, enlarge the maximum property name length in > the regulator core, so that we're able to correctly parse the > supply parents, which have got very long names (details in patch 1/5). > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [1/6] regulator: core: Enlarge max OF property name length to 64 chars commit: e9bb4a068b206f61ef01057cfeafdb852fb244c5 [2/6] regulator: qcom_spmi: Add support for new regulator types commit: 328816c2033160a6929fb0c6f0018b7c8d75cefe [3/6] regulator: qcom_spmi: Add PM660/PM660L regulators commit: 0074c4472dcb20e989d9870c0b3aba42d0aa44b8 [4/6] regulator: dt-bindings: Document the PM660/660L SPMI PMIC entries commit: f9f061a5486f6a87e32fac80223ae44d4aefc06f [5/6] regulator: qcom_smd: Add PM660/PM660L regulator support commit: 6d849653b00f2336efcd371fe85a7eb31bb094e9 [6/6] regulator: dt-bindings: Document the PM660/PM660L PMICs entries commit: f627691db72921f300e333fbbfe8349142a94807 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
