On Wed, 3 Aug 2022 01:10:59 +0300, Iskren Chernev wrote: > This patch series adds SPMI and SMD regulator support for the PM6125 found on > SM4250/SM6115 SoCs from QCom. > > This code has been tested on: > * OnePlus Nord N100 (oneplus,billie2, SoC sm4250) > * Redmi 9T (redmi,lemon, SoC sm6115) > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [01/13] dt-bindings: regulator: qcom_spmi: Improve formatting of if-then blocks commit: ac71792707226d1210127611bb622c0362cbff25 [02/13] dt-bindings: regulator: qcom_spmi: Document PM6125 PMIC commit: 5b2a085baaa15d04396889228f1e11d2cb86b916 [03/13] dt-bindings: regulator: qcom_smd: Sort compatibles alphabetically commit: 901421765ee1e5501c15a3b76ce926e0cc4967d4 [04/13] dt-bindings: regulator: qcom_smd: Document PM6125 PMIC commit: d95fe1788438cceab40af5f3f9e9fe15d8c07101 [05/13] regulator: qcom_spmi: Add support for HFSMPS regulator type commit: 2785025495b6bd630648f8304f8d932b0d0a9f2a [06/13] regulator: qcom_spmi: Add support for LDO_510 and FTSMPS commit: 0d1cf568b4e0c65cb533fef2c116fb2883803c53 [07/13] regulator: qcom_spmi: Sort pmics alphabetically (part 1) commit: 046d7e3246ac028bfe583b4c3bed9530a80004c4 [08/13] regulator: qcom_spmi: Sort pmics alphabetically (part 2) commit: 9a2da0749ce37d4a74f7becf3b09bf2e0169145a [09/13] regulator: qcom_spmi: Add PM6125 PMIC support commit: e62ef4a9f936326e702ef08ea3f65b62bd7d108b [10/13] regulator: qcom_smd: Sort pmics alphabetically (part 1) commit: 8e584e84ae65ecc9ee90b187d4b7782dc881e4ad [11/13] regulator: qcom_smd: Sort pmics alphabetically (part 2) commit: 13b3d00590243888563cb63b88538a4c60bce57b [12/13] regulator: qcom_smd: Sort pmics alphabetically (part 3) commit: a39d0100572e188f00ff4d224af9694c7eb3eeb5 [13/13] regulator: qcom_smd: Add PM6125 RPM regulators commit: 95b5f3ef4c0cf553a97dd7ce7d6ef85415388011 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
