2022-02-11 18:30:32

by Vincent Whitchurch

Subject: [PATCH] regulator: tps62864: Fix bindings for SW property

The property is not a pattern, so it should use 'properties' instead of
'patternProperties'. Also, unevaluatedProperties should be set to false
like in the other regulator bindings.

Reported-by: Rob Herring <[email protected]>
Signed-off-by: Vincent Whitchurch <[email protected]>
---
Documentation/devicetree/bindings/regulator/ti,tps62864.yaml | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/regulator/ti,tps62864.yaml b/Documentation/devicetree/bindings/regulator/ti,tps62864.yaml
index e3d739a37ab0..0f29c75f42ea 100644
--- a/Documentation/devicetree/bindings/regulator/ti,tps62864.yaml
+++ b/Documentation/devicetree/bindings/regulator/ti,tps62864.yaml
@@ -23,10 +23,11 @@ properties:
regulators:
type: object

- patternProperties:
+ properties:
"SW":
type: object
$ref: regulator.yaml#
+ unevaluatedProperties: false

additionalProperties: false

--
2.34.1

2022-02-14 19:08:31

by Mark Brown

Subject: Re: [PATCH] regulator: tps62864: Fix bindings for SW property

On Fri, 11 Feb 2022 14:24:49 +0100, Vincent Whitchurch wrote:
> The property is not a pattern, so it should use 'properties' instead of
> 'patternProperties'. Also, unevaluatedProperties should be set to false
> like in the other regulator bindings.
>
>

Applied to

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

Thanks!

[1/1] regulator: tps62864: Fix bindings for SW property
commit: a94e5cd8457fb46866459562ef6c53f9dcc375f7

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