From: Mark Brown <broonie@kernel.org>
To: Johan Jonker <jbx6244@gmail.com>
Cc: lgirdwood@gmail.com, heiko@sntech.de, robh+dt@kernel.org,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: sound: convert rockchip spdif bindings to yaml
Date: Tue, 24 Mar 2020 13:35:06 +0000 [thread overview]
Message-ID: <20200324133506.GC7039@sirena.org.uk> (raw)
In-Reply-To: <20200324123155.11858-1-jbx6244@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 397 bytes --]
On Tue, Mar 24, 2020 at 01:31:53PM +0100, Johan Jonker wrote:
> Current dts files with 'spdif' nodes are manually verified.
> In order to automate this process rockchip-spdif.txt
> has to be converted to yaml.
> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
> ---
> Changed V2:
> dmas and dma-names layout
This is the second v2 you've sent of this today - it adds these but
drops Rob's ack?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-03-24 13:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 12:31 [PATCH v2 1/3] dt-bindings: sound: convert rockchip spdif bindings to yaml Johan Jonker
2020-03-24 12:31 ` [PATCH v2 2/3] dt-bindings: sound: rockchip-spdif: add #sound-dai-cells property Johan Jonker
2020-03-31 20:01 ` Rob Herring
2020-03-24 12:31 ` [PATCH v2 3/3] dt-bindings: sound: rockchip-spdif: add power-domains property Johan Jonker
2020-03-31 20:01 ` Rob Herring
2020-03-24 13:35 ` Mark Brown [this message]
2020-03-24 13:39 ` [PATCH v2 1/3] dt-bindings: sound: convert rockchip spdif bindings to yaml Heiko Stübner
2020-03-24 13:44 ` Mark Brown
2020-03-24 13:41 ` Johan Jonker
2020-03-31 20:00 ` Rob Herring
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=20200324133506.GC7039@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).