Skip to contentSkip to conversation

regulator: dt-bindings: Revise the rt5190a buck/ldo description

PATCH In review cy_huang 2 participants 2 messages Apr 22, 2022

Subsystems (2)
lore
Share & tools
lore

cy_huang

author
#0 lore raw

PATCH 1/1 regulator: dt-bindings: Revise the rt5190a buck/ldo description

From: ChiYuan Huang <[email protected]>

Revise the rt5190a bucks and ldo property description.

---
 .../devicetree/bindings/regulator/richtek,rt5190a-regulator.yaml        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/devicetree/bindings/regulator/richtek,rt5190a-regulator.yaml +1 -1
index 28725c5..edb411b 100644
@@ -58,7 +58,7 @@ properties:
         type: object
         $ref: regulator.yaml#
         description: |
-          regulator description for buck1 and buck4.
+          regulator description for buck1 to buck4, and ldo.
 
         properties:
           regulator-allowed-modes:
Signature · 1 line
2.7.4
maintainer
#1 lore raw
Quoted 5 lines · cy_huang

From: ChiYuan Huang <[email protected]>

Revise the rt5190a bucks and ldo property description.

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: dt-bindings: Revise the rt5190a buck/ldo description

      commit: dfd2b37edf7ef469574ef7f36e3a1905ac9ead62

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