Skip to contentSkip to conversation

ASoC: dt-bindings: renesas: rsnd: Fix incorrect 'port' regex schema

PATCH In review Rob Herring 2 participants 2 messages Jul 15, 2021

Subsystems (3)
lore
Share & tools
lore

Rob Herring

author maintainer
#0 lore raw

PATCH 1/1 ASoC: dt-bindings: renesas: rsnd: Fix incorrect 'port' regex schema

A property regex goes under 'patternProperties', not 'properties' schema. Otherwise, the regex is interpretted as a fixed string.

Fixes 17c2d247ddd2 ("ASoC: dt-bindings: renesas: rsnd: tidyup properties")
Cc Mark Brown <[email protected]>
Cc Kuninori Morimoto <[email protected]>

---
I can take this as I have a few other things for -rc2.

 Documentation/devicetree/bindings/sound/renesas,rsnd.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/devicetree/bindings/sound/renesas,rsnd.yaml +1 -1
index ee936d1aa724..c2930d65728e 100644
@@ -114,7 +114,7 @@ properties:
 
   ports:
     $ref: /schemas/graph.yaml#/properties/ports
-    properties:
+    patternProperties:
       port(@[0-9a-f]+)?:
         $ref: audio-graph-port.yaml#
         unevaluatedProperties: false
Signature · 1 line
2.27.0
maintainer
#1 lore raw
Quoted 2 lines · Rob Herring

A property regex goes under 'patternProperties', not 'properties' schema. Otherwise, the regex is interpretted as a fixed string.

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] ASoC: dt-bindings: renesas: rsnd: Fix incorrect 'port' regex schema

      commit: 9a3223b0713369e6258fd8656e0c0a5ed794d186

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