dt-bindings: regulator: qcom,usb-vbus-regulator: clean up example
Subsystems (3)
PATCH 1/1 dt-bindings: regulator: qcom,usb-vbus-regulator: clean up example
Devicetree node names should be generic; fix up the qcom,usb-vbus-regulator binding example accordingly.
While at it, drop an unnecessary label and add a newline separator before the child node to improve readability.
--- .../bindings/regulator/qcom,usb-vbus-regulator.yaml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
Documentation/devicetree/bindings/regulator/qcom,usb-vbus-regulator.yaml +3 -2
@@ -36,10 +36,11 @@ unevaluatedProperties: false examples: - | - pm8150b { + pmic { #address-cells = <1>; #size-cells = <0>; - pm8150b_vbus: usb-vbus-regulator@1100 { + + usb-vbus-regulator@1100 { compatible = "qcom,pm8150b-vbus-reg"; reg = <0x1100>; regulator-min-microamp = <500000>;
Signature · 1 line
2.41.0
Mark Brown
maintainerQuoted 8 lines · Johan Hovold
Devicetree node names should be generic; fix up the qcom,usb-vbus-regulator binding example accordingly.
While at it, drop an unnecessary label and add a newline separator before the child node to improve readability.
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] dt-bindings: regulator: qcom,usb-vbus-regulator: clean up example
commit: d939c02359a656a624d03c6f14ccadae4a1c66ac
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