[PATCH] ASoC: dt-bindings: rt1015p: fix syntax error in dts-binding document

[PATCH] ASoC: dt-bindings: rt1015p: fix syntax error in dts-binding document

[Jack Yu]

Fix syntax error in dts-binding document.

Signed-off-by: Jack Yu <jack.yu@realtek.com>
---
 Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml b/Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml
index 8fcb5f79a1b5..f31d3c4d0192 100644
--- a/Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml
+++ b/Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml
@@ -16,8 +16,8 @@ description: |
 properties:
   compatible:
       oneOf:
-        const: realtek,rt1015p
-        const: realtek,rt1019p
+        - const: realtek,rt1015p
+        - const: realtek,rt1019p
 
   sdb-gpios:
     description:
-- 
2.31.1

Re: [PATCH] ASoC: dt-bindings: rt1015p: fix syntax error in dts-binding document

[Tzung-Bi Shih]

On Tue, Aug 10, 2021 at 10:08:34AM +0800, Jack Yu wrote:
> Signed-off-by: Jack Yu <jack.yu@realtek.com>
Would be better to put the tag:
Fixes: 064478e4877c ("ASoC: dt-bindings: rt1015p: add new compatible id")

>  properties:
>    compatible:
>        oneOf:
> -        const: realtek,rt1015p
> -        const: realtek,rt1019p
> +        - const: realtek,rt1015p
> +        - const: realtek,rt1019p
Not directly related to the fix but the "oneOf" has 2 extra space indent from the upper layer.

Re: [PATCH] ASoC: dt-bindings: rt1015p: fix syntax error in dts-binding document

[Mark Brown]

On Tue, 10 Aug 2021 10:08:34 +0800, Jack Yu wrote:
> Fix syntax error in dts-binding document.
> 
> 
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: dt-bindings: rt1015p: fix syntax error in dts-binding document
      commit: eb7ab747efd600382bc2e9406ea1fc2a867e9804

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