Hi, On Thu, Dec 17, 2020 at 04:34:29PM -0600, Rob Herring wrote: > The correct syntax for JSON pointers begins with a '/' after the '#'. > Without a '/', the string should be interpretted as a subschema > identifier. The jsonschema module currently doesn't handle subschema > identifiers and incorrectly allows JSON pointers to begin without a '/'. > Let's fix this before it becomes a problem when jsonschema module is > fixed. > > Converted with: > perl -p -i -e 's/yaml#definitions/yaml#\/definitions/g' `find Documentation/devicetree/bindings/ -name "*.yaml"` [...] > .../bindings/power/supply/cw2015_battery.yaml | 2 +- [...] > diff --git a/Documentation/devicetree/bindings/power/supply/cw2015_battery.yaml b/Documentation/devicetree/bindings/power/supply/cw2015_battery.yaml > index ee92e6a076ac..5fcdf5801536 100644 > --- a/Documentation/devicetree/bindings/power/supply/cw2015_battery.yaml > +++ b/Documentation/devicetree/bindings/power/supply/cw2015_battery.yaml > @@ -27,7 +27,7 @@ properties: > of this binary blob is kept secret by CellWise. The only way to obtain > it is to mail two batteries to a test facility of CellWise and receive > back a test report with the binary blob. > - $ref: /schemas/types.yaml#definitions/uint8-array > + $ref: /schemas/types.yaml#/definitions/uint8-array > minItems: 64 > maxItems: 64 > [...] Acked-by: Sebastian Reichel <sre@xxxxxxxxxx> -- Sebastian
Attachment:
signature.asc
Description: PGP signature
