dt-bindings: Remove last usage of "binding" or "schema" in titles
Subsystems (6)
Rob Herring
maintainerPATCH 1/1 dt-bindings: Remove last usage of "binding" or "schema" in titles
The Devicetree bindings document does not have to say in the title that it is a "Devicetree binding", but instead just describe the hardware.
Most of these have been fixed already, so fix the handful that snuck in. With this, a meta-schema check can be enabled to catch these automatically.
--- .../devicetree/bindings/clock/brcm,bcm63268-timer-clocks.yaml | 2 +- Documentation/devicetree/bindings/clock/imx8mp-audiomix.yaml | 2 +- .../devicetree/bindings/power/reset/restart-handler.yaml | 2 +- .../devicetree/bindings/remoteproc/ti,pru-consumer.yaml | 2 +- .../devicetree/bindings/reserved-memory/framebuffer.yaml | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-)
Documentation/devicetree/bindings/clock/brcm,bcm63268-timer-clocks.yaml +1 -1
@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/clock/brcm,bcm63268-timer-clocks.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: Broadcom BCM63268 Timer Clock and Reset Device Tree Bindings +title: Broadcom BCM63268 Timer Clock and Reset maintainers: - Álvaro Fernández Rojas <[email protected]>
Documentation/devicetree/bindings/clock/imx8mp-audiomix.yaml +1 -1
@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/clock/imx8mp-audiomix.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: NXP i.MX8MP AudioMIX Block Control Binding +title: NXP i.MX8MP AudioMIX Block Control maintainers: - Marek Vasut <[email protected]>
Documentation/devicetree/bindings/power/reset/restart-handler.yaml +1 -1
@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/power/reset/restart-handler.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: Restart and shutdown handler generic binding +title: Restart and shutdown handler Common Properties maintainers: - Sebastian Reichel <[email protected]>
Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml +1 -1
@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/remoteproc/ti,pru-consumer.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: Common TI PRU Consumer Binding +title: TI PRU Consumer Common Properties maintainers: - Suman Anna <[email protected]>
Documentation/devicetree/bindings/reserved-memory/framebuffer.yaml +1 -1
@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/reserved-memory/framebuffer.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: /reserved-memory framebuffer node bindings +title: /reserved-memory framebuffer node maintainers: - [email protected]
Signature · 1 line
2.39.2
Quoted 34 lines · Rob Herring
The Devicetree bindings document does not have to say in the title that it is a "Devicetree binding", but instead just describe the hardware.
Most of these have been fixed already, so fix the handful that snuck in. With this, a meta-schema check can be enabled to catch these automatically.
Signed-off-by Rob Herring <[email protected]>--- .../devicetree/bindings/clock/brcm,bcm63268-timer-clocks.yaml | 2 +- Documentation/devicetree/bindings/clock/imx8mp-audiomix.yaml | 2 +- .../devicetree/bindings/power/reset/restart-handler.yaml | 2 +- .../devicetree/bindings/remoteproc/ti,pru-consumer.yaml | 2 +- .../devicetree/bindings/reserved-memory/framebuffer.yaml | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-)Documentation/devicetree/bindings/clock/brcm,bcm63268-timer-clocks.yaml +1
-1@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/clock/brcm,bcm63268-timer-clocks.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: Broadcom BCM63268 Timer Clock and Reset Device Tree Bindings +title: Broadcom BCM63268 Timer Clock and Reset maintainers: - Álvaro Fernández Rojas <[email protected]>Documentation/devicetree/bindings/clock/imx8mp-audiomix.yaml +0
-0
Documentation/devicetree/bindings/clock/imx8mp-audiomix.yaml line 7
Quoted 5 lines
Documentation/devicetree/bindings/clock/imx8mp-audiomix.yaml +1
-1@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/clock/imx8mp-audiomix.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: NXP i.MX8MP AudioMIX Block Control Binding +title: NXP i.MX8MP AudioMIX Block Control
For AudioMIX:
Documentation/devicetree/bindings/power/reset/restart-handler.yaml line 7
Quoted 2 lines · Rob Herring
Documentation/devicetree/bindings/power/reset/restart-handler.yaml +1
-1-title: Restart and shutdown handler generic binding +title: Restart and shutdown handler Common Properties
With the new caps for Common Properties, the title here looks a bit odd. Should probably be s/shutdown handler/Shutdown Handler/ for title case, but w/e...
Cheers,
Conor.
Quoted 16 lines · Rob Herring
The Devicetree bindings document does not have to say in the title that it is a "Devicetree binding", but instead just describe the hardware.
Most of these have been fixed already, so fix the handful that snuck in. With this, a meta-schema check can be enabled to catch these automatically.
Signed-off-by Rob Herring <[email protected]>--- .../devicetree/bindings/clock/brcm,bcm63268-timer-clocks.yaml | 2 +- Documentation/devicetree/bindings/clock/imx8mp-audiomix.yaml | 2 +- .../devicetree/bindings/power/reset/restart-handler.yaml | 2 +- .../devicetree/bindings/remoteproc/ti,pru-consumer.yaml | 2 +- .../devicetree/bindings/reserved-memory/framebuffer.yaml | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-)
...
Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml line 10
Quoted 13 lines
Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml +1
-1@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/remoteproc/ti,pru-consumer.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: Common TI PRU Consumer Binding +title: TI PRU Consumer Common Properties maintainers: - Suman Anna <[email protected]>
For PRU Consumer binding,
regards
Suman
Hi,
Quoted 15 lines · Rob Herring
The Devicetree bindings document does not have to say in the title that it is a "Devicetree binding", but instead just describe the hardware.
Most of these have been fixed already, so fix the handful that snuck in. With this, a meta-schema check can be enabled to catch these automatically.
Signed-off-by Rob Herring <[email protected]>--- .../devicetree/bindings/clock/brcm,bcm63268-timer-clocks.yaml | 2 +- Documentation/devicetree/bindings/clock/imx8mp-audiomix.yaml | 2 +- .../devicetree/bindings/power/reset/restart-handler.yaml | 2 +- .../devicetree/bindings/remoteproc/ti,pru-consumer.yaml | 2 +- .../devicetree/bindings/reserved-memory/framebuffer.yaml | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-)
...
Documentation/devicetree/bindings/power/reset/restart-handler.yaml line 10
Quoted 13 lines
Documentation/devicetree/bindings/power/reset/restart-handler.yaml +1
-1@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/power/reset/restart-handler.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: Restart and shutdown handler generic binding +title: Restart and shutdown handler Common Properties maintainers: - Sebastian Reichel <[email protected]>
-- Sebastian
Quoted 61 lines · Rob Herring
The Devicetree bindings document does not have to say in the title that it is a "Devicetree binding", but instead just describe the hardware.
Most of these have been fixed already, so fix the handful that snuck in. With this, a meta-schema check can be enabled to catch these automatically.
Signed-off-by Rob Herring <[email protected]>--- .../devicetree/bindings/clock/brcm,bcm63268-timer-clocks.yaml | 2 +- Documentation/devicetree/bindings/clock/imx8mp-audiomix.yaml | 2 +- .../devicetree/bindings/power/reset/restart-handler.yaml | 2 +- .../devicetree/bindings/remoteproc/ti,pru-consumer.yaml | 2 +- .../devicetree/bindings/reserved-memory/framebuffer.yaml | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-)Documentation/devicetree/bindings/clock/brcm,bcm63268-timer-clocks.yaml +1
-1@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/clock/brcm,bcm63268-timer-clocks.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: Broadcom BCM63268 Timer Clock and Reset Device Tree Bindings +title: Broadcom BCM63268 Timer Clock and Reset maintainers: - Álvaro Fernández Rojas <[email protected]>Documentation/devicetree/bindings/clock/imx8mp-audiomix.yaml +1
-1@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/clock/imx8mp-audiomix.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: NXP i.MX8MP AudioMIX Block Control Binding +title: NXP i.MX8MP AudioMIX Block Control maintainers: - Marek Vasut <[email protected]>Documentation/devicetree/bindings/power/reset/restart-handler.yaml +1
-1@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/power/reset/restart-handler.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: Restart and shutdown handler generic binding +title: Restart and shutdown handler Common Properties maintainers: - Sebastian Reichel <[email protected]>Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml +0
-0
Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml line 8
Quoted 6 lines
Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml +1
-1@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/remoteproc/ti,pru-consumer.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: Common TI PRU Consumer Binding +title: TI PRU Consumer Common Properties
Quoted 18 lines
Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml +0
-0maintainers: - Suman Anna <[email protected]>Documentation/devicetree/bindings/reserved-memory/framebuffer.yaml +1
-2@@ -4,7 +4,7 @@ $id: http://devicetree.org/schemas/reserved-memory/framebuffer.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: /reserved-memory framebuffer node bindings +title: /reserved-memory framebuffer node maintainers: - [email protected] --2.39.2
Quoting Rob Herring (2023-06-15 14:31:54)
Quoted 9 lines
The Devicetree bindings document does not have to say in the title that it is a "Devicetree binding", but instead just describe the hardware.
Most of these have been fixed already, so fix the handful that snuck in. With this, a meta-schema check can be enabled to catch these automatically.
Signed-off-by Rob Herring <[email protected]>---
Quoted 7 lines · Rob Herring
The Devicetree bindings document does not have to say in the title that it is a "Devicetree binding", but instead just describe the hardware.
Most of these have been fixed already, so fix the handful that snuck in. With this, a meta-schema check can be enabled to catch these automatically.
Quoted 9 lines
Signed-off-by Rob Herring <[email protected]>--- .../devicetree/bindings/clock/brcm,bcm63268-timer-clocks.yaml | 2 +- Documentation/devicetree/bindings/clock/imx8mp-audiomix.yaml | 2 +- .../devicetree/bindings/power/reset/restart-handler.yaml | 2 +- .../devicetree/bindings/remoteproc/ti,pru-consumer.yaml | 2 +- .../devicetree/bindings/reserved-memory/framebuffer.yaml | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-)
Applied, thanks!