The word "or" is useless and breaks yaml validation.
Signed-off-by: Corentin Labbe <[email protected]>
---
Documentation/devicetree/bindings/sound/tas27xx.yaml | 1 -
1 file changed, 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/sound/tas27xx.yaml b/Documentation/devicetree/bindings/sound/tas27xx.yaml
index 191f4bceb4ee..66a0df8850ea 100644
--- a/Documentation/devicetree/bindings/sound/tas27xx.yaml
+++ b/Documentation/devicetree/bindings/sound/tas27xx.yaml
@@ -20,7 +20,6 @@ properties:
compatible:
enum:
- ti,tas2764
- or
- ti,tas2780
reg:
--
2.35.1
On 11/04/2022 21:44, Corentin Labbe wrote:
> The word "or" is useless and breaks yaml validation.
>
> Signed-off-by: Corentin Labbe <[email protected]>
> ---
> Documentation/devicetree/bindings/sound/tas27xx.yaml | 1 -
> 1 file changed, 1 deletion(-)
>
Subject should be reversed for this subsystem, so:
"ASoC; dt-bindings: tas27xx:"
Reviewed-by: Krzysztof Kozlowski <[email protected]>
Best regards,
Krzysztof
On Mon, 11 Apr 2022 19:44:09 +0000, Corentin Labbe wrote:
> The word "or" is useless and breaks yaml validation.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] dt-bindings: ASoC: fix invalid yaml
commit: 506840600613027f139d30447a2c27ec8088c698
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