From: Biju Das <biju.das@bp.renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Simon Horman <horms@verge.net.au>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH] dt-bindings: dmaengine: rcar-dmac: Document R8A774B1 bindings
Date: Thu, 26 Sep 2019 14:09:24 +0000 [thread overview]
Message-ID: <OSBPR01MB210380CE9A07266238A03B41B8860@OSBPR01MB2103.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAMuHMdW+AwUFTbN6+084jZdYdVHYdi1wzBGAxkreqcQCGXm8zw@mail.gmail.com>
Hi Geert,
Thanks for the feedback.
> Subject: Re: [PATCH] dt-bindings: dmaengine: rcar-dmac: Document
> R8A774B1 bindings
>
> On Mon, Sep 23, 2019 at 3:24 PM Biju Das <biju.das@bp.renesas.com>
> wrote:
> > Renesas RZ/G2N (R8A774B1) SoC has DMA controllers compatible with this
> > driver, therefore document RZ/G2N specific bindings.
>
> Please don't mention "driver", as DT bindings are intended to be
> implementation-agnostic.
OK. Will send V2 without mentioning "driver".
> > Signed-off-by: Biju Das <biju.das@bp.renesas.com>
>
> For the actual change:
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Regards,
Biju
prev parent reply other threads:[~2019-09-26 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 13:24 [PATCH] dt-bindings: dmaengine: rcar-dmac: Document R8A774B1 bindings Biju Das
2019-09-26 12:29 ` Geert Uytterhoeven
2019-09-26 14:09 ` Biju Das [this message]
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=OSBPR01MB210380CE9A07266238A03B41B8860@OSBPR01MB2103.jpnprd01.prod.outlook.com \
--to=biju.das@bp.renesas.com \
--cc=Chris.Paterson2@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=vkoul@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).