Re: [PATCH] dt-bindings: Fix JSON pointers

2020-12-19 Thread Pavel Machek
On Thu 2020-12-17 16:34:29, 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 p

Re: [PATCH] dt-bindings: Fix JSON pointers

2020-12-18 Thread Jakub Kicinski
On Thu, 17 Dec 2020 16:34:29 -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

Re: [PATCH] dt-bindings: Fix JSON pointers

2020-12-18 Thread Mark Brown
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

Re: [PATCH] dt-bindings: Fix JSON pointers

2020-12-18 Thread Florian Fainelli
On 12/17/20 2:34 PM, 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

Re: [PATCH] dt-bindings: Fix JSON pointers

2020-12-18 Thread Sebastian Reichel
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 incorr

Re: [PATCH] dt-bindings: Fix JSON pointers

2020-12-18 Thread Guenter Roeck
On 12/17/20 2:34 PM, 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

Re: [PATCH] dt-bindings: Fix JSON pointers

2020-12-18 Thread Lee Jones
On Thu, 17 Dec 2020, 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 pointer

Re: [PATCH] dt-bindings: Fix JSON pointers

2020-12-17 Thread Vinod Koul
On 17-12-20, 16:34, 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

[PATCH] dt-bindings: Fix JSON pointers

2020-12-17 Thread Rob Herring
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 i