From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: linux-sound@vger.kernel.org,
Maruthi Srinivas Bayyavarapu
<maruthi.srinivas.bayyavarapu@xilinx.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/4] ASoC: dt-bindings: xlnx,spdif: Convert to json-schema
Date: Wed, 26 Feb 2025 12:25:19 +0000 [thread overview]
Message-ID: <01eec26d-9ddd-4ef4-b921-dd7ff4dd0e23@arm.com> (raw)
In-Reply-To: <20250225221945.GB3224894-robh@kernel.org>
Hi Rob
On 25/02/2025 22:19, Rob Herring wrote:
> This was in the example, but otherwise wasn't documented before. And the
> Linux driver doesn't need it. So let's drop 'interrupt-names' because it
> is pointless here. 'spdif' is redundant because this the the spdif
> block. 'interrupt' is redundant because it's only interrupts in this
> list.
>
> Don't forget the example.
>
> With that,
>
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
Thank you for your help!
--
Regards,
Vincenzo
next prev parent reply other threads:[~2025-02-26 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 19:07 [PATCH v5 0/4] xlnx: dt-bindings: Convert to json-schema Vincenzo Frascino
2025-02-25 19:07 ` [PATCH v5 1/4] ASoC: dt-bindings: xlnx,i2s: " Vincenzo Frascino
2025-02-25 19:07 ` [PATCH v5 2/4] ASoC: dt-bindings: xlnx,audio-formatter: " Vincenzo Frascino
2025-02-25 22:14 ` Rob Herring
2025-02-25 19:07 ` [PATCH v5 3/4] ASoC: dt-bindings: xlnx,spdif: " Vincenzo Frascino
2025-02-25 22:19 ` Rob Herring
2025-02-26 12:25 ` Vincenzo Frascino [this message]
2025-02-25 19:07 ` [PATCH v5 4/4] MAINTAINERS: Add Vincenzo Frascino as Xilinx Sound Driver Maintainer Vincenzo Frascino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01eec26d-9ddd-4ef4-b921-dd7ff4dd0e23@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=maruthi.srinivas.bayyavarapu@xilinx.com \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox