From: Rob Herring <robh@kernel.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Frank Rowand <frowand.list@gmail.com>,
Katsuhiro Suzuki <katsuhiro@katsuster.net>,
devicetree@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, - <alsa-devel@alsa-project.org>,
linux-arm-kernel@lists.infradead.org,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2] dt-bindings: ASoC: Convert UniPhier EVEA codec to json-schema
Date: Mon, 13 Jul 2020 20:22:52 -0600 [thread overview]
Message-ID: <20200714022252.GA1151466@bogus> (raw)
In-Reply-To: <20200623114005.791643-1-yamada.masahiro@socionext.com>
On Tue, 23 Jun 2020 20:40:05 +0900, Masahiro Yamada wrote:
> Convert the UniPhier EVEA sound codec binding to DT schema format.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
> Changes in v2:
> - Add schema for subnode 'port'
>
> .../sound/socionext,uniphier-evea.yaml | 70 +++++++++++++++++++
> .../bindings/sound/uniphier,evea.txt | 26 -------
> 2 files changed, 70 insertions(+), 26 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/sound/socionext,uniphier-evea.yaml
> delete mode 100644 Documentation/devicetree/bindings/sound/uniphier,evea.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-07-14 2:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 11:40 [PATCH v2] dt-bindings: ASoC: Convert UniPhier EVEA codec to json-schema Masahiro Yamada
2020-07-14 2:22 ` Rob Herring [this message]
2020-07-14 6:13 ` Masahiro Yamada
2020-07-14 9:52 ` Mark Brown
2020-07-14 11:08 ` Masahiro Yamada
2020-07-14 11:31 ` Mark Brown
2020-07-14 17:52 ` Rob Herring
2020-07-14 16:39 ` Mark Brown
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=20200714022252.GA1151466@bogus \
--to=robh@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=katsuhiro@katsuster.net \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).