Documentation/devicetree/bindings/input/azoteq,iqs7222.yaml | 2 +- Documentation/devicetree/bindings/media/amphion,vpu.yaml | 2 +- Documentation/devicetree/bindings/mtd/mtd.yaml | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-)
When referencing other schema, it is preferred to use an absolute path
(/schemas/....), which allows also an seamless move of particular schema
out of Linux kernel to dtschema.
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
---
Rob, maybe you can take it directly? Should apply cleanly on your tree.
---
Documentation/devicetree/bindings/input/azoteq,iqs7222.yaml | 2 +-
Documentation/devicetree/bindings/media/amphion,vpu.yaml | 2 +-
Documentation/devicetree/bindings/mtd/mtd.yaml | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/input/azoteq,iqs7222.yaml b/Documentation/devicetree/bindings/input/azoteq,iqs7222.yaml
index 5b1769c19b17..418c168b223b 100644
--- a/Documentation/devicetree/bindings/input/azoteq,iqs7222.yaml
+++ b/Documentation/devicetree/bindings/input/azoteq,iqs7222.yaml
@@ -784,7 +784,7 @@ patternProperties:
gpio-2: GPIO4
allOf:
- - $ref: ../pinctrl/pincfg-node.yaml#
+ - $ref: /schemas/pinctrl/pincfg-node.yaml#
properties:
drive-open-drain: true
diff --git a/Documentation/devicetree/bindings/media/amphion,vpu.yaml b/Documentation/devicetree/bindings/media/amphion,vpu.yaml
index c0d83d755239..9801de3ed84e 100644
--- a/Documentation/devicetree/bindings/media/amphion,vpu.yaml
+++ b/Documentation/devicetree/bindings/media/amphion,vpu.yaml
@@ -44,7 +44,7 @@ patternProperties:
description:
Each vpu encoder or decoder correspond a MU, which used for communication
between driver and firmware. Implement via mailbox on driver.
- $ref: ../mailbox/fsl,mu.yaml#
+ $ref: /schemas/mailbox/fsl,mu.yaml#
"^vpu-core@[0-9a-f]+$":
diff --git a/Documentation/devicetree/bindings/mtd/mtd.yaml b/Documentation/devicetree/bindings/mtd/mtd.yaml
index ee442ecb11cd..bbb56216a4e2 100644
--- a/Documentation/devicetree/bindings/mtd/mtd.yaml
+++ b/Documentation/devicetree/bindings/mtd/mtd.yaml
@@ -48,8 +48,8 @@ patternProperties:
type: object
allOf:
- - $ref: ../nvmem/nvmem.yaml#
- - $ref: ../nvmem/nvmem-deprecated-cells.yaml#
+ - $ref: /schemas/nvmem/nvmem.yaml#
+ - $ref: /schemas/nvmem/nvmem-deprecated-cells.yaml#
unevaluatedProperties: false
--
2.43.0
On Sun, 05 May 2024 10:46:18 +0200, Krzysztof Kozlowski wrote: > When referencing other schema, it is preferred to use an absolute path > (/schemas/....), which allows also an seamless move of particular schema > out of Linux kernel to dtschema. > > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > > --- > > Rob, maybe you can take it directly? Should apply cleanly on your tree. > --- > Documentation/devicetree/bindings/input/azoteq,iqs7222.yaml | 2 +- > Documentation/devicetree/bindings/media/amphion,vpu.yaml | 2 +- > Documentation/devicetree/bindings/mtd/mtd.yaml | 4 ++-- > 3 files changed, 4 insertions(+), 4 deletions(-) > Applied, thanks!
Hi Krzysztof, krzysztof.kozlowski@linaro.org wrote on Sun, 5 May 2024 10:46:18 +0200: > When referencing other schema, it is preferred to use an absolute path > (/schemas/....), which allows also an seamless move of particular schema > out of Linux kernel to dtschema. I didn't know about this. You probably want to add a check over uses of relative paths in the tooling now :-) > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > > --- > > Rob, maybe you can take it directly? Should apply cleanly on your tree. Acked-by: Miquel Raynal <miquel.raynal@bootlin.com> Thanks, Miquèl
© 2016 - 2024 Red Hat, Inc.