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

Rob Herring posted 1 patch 4 years, 6 months ago
.../devicetree/bindings/regulator/samsung,s5m8767.yaml         | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
[PATCH] regulator: dt-bindings: samsung,s5m8767: Move fixed string BUCK9 to 'properties'
Posted by Rob Herring 4 years, 6 months ago
There's no need for a fixed string like 'BUCK9' to be under
'patternProperties', so move it under 'properties' instead.

Signed-off-by: Rob Herring <robh@kernel.org>
---
 .../devicetree/bindings/regulator/samsung,s5m8767.yaml         | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/regulator/samsung,s5m8767.yaml b/Documentation/devicetree/bindings/regulator/samsung,s5m8767.yaml
index 80a63d47790a..6c8ad82bd69c 100644
--- a/Documentation/devicetree/bindings/regulator/samsung,s5m8767.yaml
+++ b/Documentation/devicetree/bindings/regulator/samsung,s5m8767.yaml
@@ -54,8 +54,9 @@ patternProperties:
     required:
       - regulator-name
 
+properties:
   # 9 buck
-  "^BUCK9$":
+  BUCK9:
     type: object
     $ref: regulator.yaml#
     unevaluatedProperties: false
-- 
2.32.0

Re: [PATCH] regulator: dt-bindings: samsung,s5m8767: Move fixed string BUCK9 to 'properties'
Posted by Mark Brown 4 years, 6 months ago
On Tue, 21 Dec 2021 08:07:43 -0400, Rob Herring wrote:
> 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