dt-bindings: spi-mux: Add reference to spi-peripheral-props.yaml schema
Subsystems (2)
Rob Herring
maintainerPATCH 1/1 dt-bindings: spi-mux: Add reference to spi-peripheral-props.yaml schema
The spi-mux serves as both a SPI peripheral and controller, so add a reference to spi-peripheral-props.yaml in addition to spi-controller.yaml. This is necessary to avoid unevaluatedProperties warnings once those are fully enabled.
--- Documentation/devicetree/bindings/spi/spi-mux.yaml | 1 + 1 file changed, 1 insertion(+)
Documentation/devicetree/bindings/spi/spi-mux.yaml +1 -0
@@ -31,6 +31,7 @@ description: | allOf: - $ref: "/schemas/spi/spi-controller.yaml#" + - $ref: "/schemas/spi/spi-peripheral-props.yaml#" maintainers: - Chris Packham <[email protected]>
Signature · 1 line
2.32.0
Quoted 9 lines · Rob Herring
The spi-mux serves as both a SPI peripheral and controller, so add a reference to
spi-peripheral-props.yamlin addition tospi-controller.yaml. This is necessary to avoid unevaluatedProperties warnings once those are fully enabled.Cc Mark Brown <[email protected]>Cc Chris Packham <[email protected]>Signed-off-by Rob Herring <[email protected]>
Quoted 16 lines
--- Documentation/devicetree/bindings/spi/spi-mux.yaml | 1 + 1 file changed, 1 insertion(+)Documentation/devicetree/bindings/spi/spi-mux.yaml +1
-0@@ -31,6 +31,7 @@ description: | allOf: - $ref: "/schemas/spi/spi-controller.yaml#" + - $ref: "/schemas/spi/spi-peripheral-props.yaml#" maintainers: - Chris Packham <[email protected]>
Mark Brown
maintainerQuoted 6 lines · Rob Herring
The spi-mux serves as both a SPI peripheral and controller, so add a reference to
spi-peripheral-props.yamlin addition tospi-controller.yaml. This is necessary to avoid unevaluatedProperties warnings once those are fully enabled.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] dt-bindings: spi-mux: Add reference to spi-peripheral-props.yaml schema
commit: 709c81b55c6aa74a6cdad27bdc224f50962b6ad9
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark