A valid JSON pointer should begin with a '/'. The json-schema package is
lax on this allowing either form, but that's changing in new versions.
Signed-off-by: Rob Herring <[email protected]>
---
Documentation/devicetree/bindings/leds/common.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/leds/common.yaml b/Documentation/devicetree/bindings/leds/common.yaml
index c8d0ba5f2327..55a8d1385e21 100644
--- a/Documentation/devicetree/bindings/leds/common.yaml
+++ b/Documentation/devicetree/bindings/leds/common.yaml
@@ -167,7 +167,7 @@ properties:
Note that this flag is mainly used for PWM-LEDs, where it is not possible
to map brightness to current. Drivers for other controllers should use
led-max-microamp.
- $ref: /schemas/types.yaml#definitions/uint32
+ $ref: /schemas/types.yaml#/definitions/uint32
panic-indicator:
description:
--
2.42.0
On 22/11/2023 21:54, Rob Herring wrote:
> A valid JSON pointer should begin with a '/'. The json-schema package is
> lax on this allowing either form, but that's changing in new versions.
>
> Signed-off-by: Rob Herring <[email protected]>
Reviewed-by: Krzysztof Kozlowski <[email protected]>
Best regards,
Krzysztof
On Wed, 22 Nov 2023 13:54:17 -0700, Rob Herring wrote:
> A valid JSON pointer should begin with a '/'. The json-schema package is
> lax on this allowing either form, but that's changing in new versions.
>
>
Applied, thanks!
[1/1] dt-bindings: leds: Fix JSON pointer in max-brightness
commit: 2dc0a14846ecf85fb4de29be186581f008d197dd
--
Lee Jones [李琼斯]