From: Biju Das <biju.das@bp.renesas.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Linux I2C <linux-i2c@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.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: i2c: rcar: Add r8a774b1 support
Date: Fri, 4 Oct 2019 06:37:32 +0000 [thread overview]
Message-ID: <OSBPR01MB2103AD1CECA6DCD0C1BCE067B89E0@OSBPR01MB2103.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <OSBPR01MB2103237D77ECCD14A41EEFFAB8860@OSBPR01MB2103.jpnprd01.prod.outlook.com>
Hi Wolfram,
Do you want me to send V2? Or Are you happy to fix this while applying this patch against changed file name?
Please let me know.
Regards,
Biju
> Subject: RE: [PATCH] dt-bindings: i2c: rcar: Add r8a774b1 support
>
> Hi Geert,
>
> Thanks for the feedback.
>
> > Subject: Re: [PATCH] dt-bindings: i2c: rcar: Add r8a774b1 support
> >
> > On Tue, Sep 24, 2019 at 9:33 AM Biju Das <biju.das@bp.renesas.com>
> wrote:
> > > Document RZ/G2N (R8A774B1) I2C compatibility with the relevant
> > > driver dt-bindings.
> > >
> > > Signed-off-by: Biju Das <biju.das@bp.renesas.com>
> >
> > Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >
> > > Documentation/devicetree/bindings/i2c/i2c-rcar.txt | 1 +
> >
> > BTW, this file has been renamed to
> > Documentation/devicetree/bindings/i2c/renesas,i2c.txt
>
> OK. Will send V2 with the above file change.
>
> Regards,
> Biju
next prev parent reply other threads:[~2019-10-04 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 7:32 [PATCH] dt-bindings: i2c: rcar: Add r8a774b1 support Biju Das
2019-09-26 12:42 ` Geert Uytterhoeven
2019-09-26 12:48 ` Biju Das
2019-10-04 6:37 ` Biju Das [this message]
2019-10-04 7:07 ` Wolfram Sang
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=OSBPR01MB2103AD1CECA6DCD0C1BCE067B89E0@OSBPR01MB2103.jpnprd01.prod.outlook.com \
--to=biju.das@bp.renesas.com \
--cc=Chris.Paterson2@renesas.com \
--cc=devicetree@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-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wsa+renesas@sang-engineering.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).