From: Mark Brown <broonie@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Katsuhiro Suzuki <katsuhiro@katsuster.net>,
DTML <devicetree@vger.kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
- <alsa-devel@alsa-project.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2] dt-bindings: ASoC: Convert UniPhier EVEA codec to json-schema
Date: Tue, 14 Jul 2020 12:31:24 +0100 [thread overview]
Message-ID: <20200714113124.GD4900@sirena.org.uk> (raw)
In-Reply-To: <CAK7LNARUwPRtG0uMZ4rwr7=+3wa9X1B70AXbnFL-CF1_wMvevw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
On Tue, Jul 14, 2020 at 08:08:45PM +0900, Masahiro Yamada wrote:
> On Tue, Jul 14, 2020 at 6:53 PM Mark Brown <broonie@kernel.org> wrote:
> > 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.
> OK, then please apply the following two if they look good.
> https://lore.kernel.org/patchwork/patch/1261568/
> https://lore.kernel.org/patchwork/patch/1261569/
> Both got Rob's Reviewed-by.
Only today...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-14 11:31 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
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 [this message]
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=20200714113124.GD4900@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).