From: Biju Das <biju.das.jz@bp.renesas.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Chris Brandt <Chris.Brandt@renesas.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Linux-ALSA <alsa-devel@alsa-project.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"open list:MEDIA DRIVERS FOR RENESAS - FCP"
<linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH 1/9] ASoC: dt-bindings: Document RZ/G2L bindings
Date: Mon, 19 Jul 2021 13:43:50 +0000 [thread overview]
Message-ID: <OS0PR01MB59220B479B4DB8D2C1348CF886E19@OS0PR01MB5922.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAL_JsqKWzxVzrK+p3USL_nK28hf1JMq_P=zJmtCD2d+SufTzRA@mail.gmail.com>
Hi Rob,
Thanks for the feedback.
> -----Original Message-----
> From: Rob Herring <robh+dt@kernel.org>
> Sent: 02 July 2021 22:23
> To: Biju Das <biju.das.jz@bp.renesas.com>
> Cc: Liam Girdwood <lgirdwood@gmail.com>; Mark Brown <broonie@kernel.org>;
> Chris Brandt <Chris.Brandt@renesas.com>; Kuninori Morimoto
> <kuninori.morimoto.gx@renesas.com>; Linux-ALSA <alsa-devel@alsa-
> project.org>; devicetree@vger.kernel.org; Geert Uytterhoeven
> <geert+renesas@glider.be>; Chris Paterson <Chris.Paterson2@renesas.com>;
> Biju Das <biju.das@bp.renesas.com>; Prabhakar Mahadev Lad
> <prabhakar.mahadev-lad.rj@bp.renesas.com>; open list:MEDIA DRIVERS FOR
> RENESAS - FCP <linux-renesas-soc@vger.kernel.org>
> Subject: Re: [PATCH 1/9] ASoC: dt-bindings: Document RZ/G2L bindings
>
> On Fri, Jul 2, 2021 at 7:50 AM Biju Das <biju.das.jz@bp.renesas.com>
> wrote:
> >
> > Document RZ/G2L ASoC serial sound interface bindings.
> >
> > Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> > Reviewed-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> > ---
> > Note:- This patch has dependency on #include
> > <dt-bindings/clock/r9a07g044-cpg.h> file which will be in next
> > 5.14-rc1 release
>
> That kind of means you should wait and send this once v5.14-rc1 is
> released as it is the merge window currently.
Sure. Will do.
Cheers,
Biju
next prev parent reply other threads:[~2021-07-19 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 13:50 [PATCH 0/9] Add RZ/G2L Sound support Biju Das
2021-07-02 13:50 ` [PATCH 1/9] ASoC: dt-bindings: Document RZ/G2L bindings Biju Das
2021-07-02 21:23 ` Rob Herring
2021-07-19 13:43 ` Biju Das [this message]
2021-07-02 13:50 ` [PATCH 4/9] arm64: dts: renesas: r9a07g044: Add external audio clock nodes Biju Das
2021-07-02 13:50 ` [PATCH 5/9] arm64: dts: renesas: r9a07g044: Add SSI support Biju Das
2021-07-02 13:50 ` [PATCH 7/9] ASoC: dt-bindings: sound: renesas,rz-ssi: Document DMA support Biju Das
2021-07-02 13:50 ` [PATCH 9/9] arm64: dts: renesas: r9a07g044: Add SSI " Biju Das
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=OS0PR01MB59220B479B4DB8D2C1348CF886E19@OS0PR01MB5922.jpnprd01.prod.outlook.com \
--to=biju.das.jz@bp.renesas.com \
--cc=Chris.Brandt@renesas.com \
--cc=Chris.Paterson2@renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=biju.das@bp.renesas.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--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).