Skip to contentSkip to conversation

regulator: dt-bindings: samsung,s5m8767: Move fixed string BUCK9 to 'properties'

PATCH In review Rob Herring 2 participants 2 messages Dec 21, 2021

Subsystems (4)
lore
Share & tools
lore

Rob Herring

author maintainer
#0 lore raw

PATCH 1/1 regulator: dt-bindings: samsung,s5m8767: Move fixed string BUCK9 to 'properties'

There's no need for a fixed string like 'BUCK9' to be under 'patternProperties', so move it under 'properties' instead.

---
 .../devicetree/bindings/regulator/samsung,s5m8767.yaml         | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
Documentation/devicetree/bindings/regulator/samsung,s5m8767.yaml +2 -1
index 80a63d47790a..6c8ad82bd69c 100644
@@ -54,8 +54,9 @@ patternProperties:
     required:
       - regulator-name
 
+properties:
   # 9 buck
-  "^BUCK9$":
+  BUCK9:
     type: object
     $ref: regulator.yaml#
     unevaluatedProperties: false
Signature · 1 line
2.32.0
maintainer
#1 lore raw
Quoted 4 lines · Rob Herring

There's no need for a fixed string like 'BUCK9' to be under 'patternProperties', so move it under 'properties' instead.

Applied to

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

Thanks!

[1/1] regulator: dt-bindings: samsung,s5m8767: Move fixed string BUCK9 to 'properties'

      commit: 5d55cbc720cc3650aafed6c1f5dbcf7e3f276312

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