Skip to contentSkip to conversation

regulator: sm5703: Correct reference to the common regulator schema

PATCH In review Markuss Broks 2 participants 2 messages Apr 29, 2022

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 regulator: sm5703: Correct reference to the common regulator schema

The correct file name is regulator.yaml, not regulators.yaml.

---
 .../bindings/regulator/siliconmitus,sm5703-regulator.yaml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
Documentation/devicetree/bindings/regulator/siliconmitus,sm5703-regulator.yaml +4 -4
index 75ff16b58000..9d84117530ca 100644
@@ -19,14 +19,14 @@ description: |
 properties:
   buck:
     type: object
-    $ref: regulators.yaml#
+    $ref: regulator.yaml#
     unevaluatedProperties: false
     description:
       Properties for the BUCK regulator.
 
   vbus:
     type: object
-    $ref: regulators.yaml#
+    $ref: regulator.yaml#
     unevaluatedProperties: false
     description:
       Properties for the VBUS regulator.
@@ -34,14 +34,14 @@ properties:
 patternProperties:
   "^ldo[1-3]$":
     type: object
-    $ref: regulators.yaml#
+    $ref: regulator.yaml#
     unevaluatedProperties: false
     description:
       Properties for single LDO regulator.
 
   "^usbldo[1-2]$":
     type: object
-    $ref: regulators.yaml#
+    $ref: regulator.yaml#
     unevaluatedProperties: false
     description:
       Properties for a single USBLDO regulator.
Signature · 1 line
2.35.1
maintainer
#1 lore raw
Quoted 3 lines · Markuss Broks

The correct file name is regulator.yaml, not regulators.yaml.

Applied to

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

Thanks!

[1/1] regulator: sm5703: Correct reference to the common regulator schema

      commit: dc6d04619e62825083926929d88c94c5b6b42670

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