From: Mark Brown <broonie@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Rob Herring <robh@kernel.org>, - <alsa-devel@alsa-project.org>,
DTML <devicetree@vger.kernel.org>,
Katsuhiro Suzuki <katsuhiro@katsuster.net>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] dt-bindings: ASoC: Convert UniPhier EVEA codec to json-schema
Date: Tue, 14 Jul 2020 10:52:59 +0100 [thread overview]
Message-ID: <20200714095259.GB4900@sirena.org.uk> (raw)
In-Reply-To: <CAK7LNAQrdqztMrHtAHnbMkxeaDLLyBS68WVovev+zytHdD7RVQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 365 bytes --]
On Tue, Jul 14, 2020 at 03:13:26PM +0900, Masahiro Yamada wrote:
> What do you mean by Reviewed-by ?
> Do you expect this to go to the asoc tree?
> I just thought the schema conversion
> would go through the dt tree.
No, bindings changes usually go through the subsystem - if there's any
other work on the binding then it'll usually also involve driver
changes.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-14 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200623114005.791643-1-yamada.masahiro@socionext.com>
2020-07-14 2:22 ` [PATCH v2] dt-bindings: ASoC: Convert UniPhier EVEA codec to json-schema Rob Herring
2020-07-14 6:13 ` Masahiro Yamada
2020-07-14 9:52 ` Mark Brown [this message]
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=20200714095259.GB4900@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.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=masahiroy@kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@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).