Skip to contentSkip to conversation

regulator: rtq6752: Refine binding document

PATCH In review cy_huang 2 participants 2 messages Jul 14, 2021

Subsystems (2)
lore
Share & tools
lore

cy_huang

author
#0 lore raw

PATCH 1/1 regulator: rtq6752: Refine binding document

From: ChiYuan Huang <[email protected]>

Drop regulators property reference and remove the status in example dts.

---
Following by the below comment to update the binding document.
Link: /https://lore.kernel.org/linux-devicetree/[email protected]/

---
 .../devicetree/bindings/regulator/richtek,rtq6752-regulator.yaml        | 2 --
 1 file changed, 2 deletions(-)
Documentation/devicetree/bindings/regulator/richtek,rtq6752-regulator.yaml +0 -2
index 641840e..e6e5a9a 100644
@@ -30,7 +30,6 @@ properties:
 
   regulators:
     type: object
-    $ref: regulator.yaml#
 
     patternProperties:
       "^(p|n)avdd$":
@@ -56,7 +55,6 @@ examples:
 
       rtq6752@6b {
         compatible = "richtek,rtq6752";
-        status = "okay";
         reg = <0x6b>;
         enable-gpios = <&gpio26 2 0>;
 
Signature · 1 line
2.7.4
maintainer
#1 lore raw
Quoted 1 line · cy_huang

Drop regulators property reference and remove the status in example dts.

Applied to

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

Thanks!

[1/1] regulator: rtq6752: Refine binding document

      commit: e98fb032170bfa2e671a01e356a7ee86a2038312

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