From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Biju Das <biju.das@bp.renesas.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Simon Horman <horms@verge.net.au>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
"devicetree\@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-renesas-soc\@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: RE: [PATCH] usb: renesas_usbhs: Add compatible string for r8a7743/5
Date: Tue, 17 Oct 2017 12:39:49 +0300 [thread overview]
Message-ID: <87fuaijeoq.fsf@linux.intel.com> (raw)
In-Reply-To: <KL1PR06MB170284D41F8517AD9A96E8A0B84C0@KL1PR06MB1702.apcprd06.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1797 bytes --]
Hi,
Biju Das <biju.das@bp.renesas.com> writes:
> Hi,
>
>> -----Original Message-----
>> From: devicetree-owner@vger.kernel.org [mailto:devicetree-
>> owner@vger.kernel.org] On Behalf Of Felipe Balbi
>> Sent: 17 October 2017 09:26
>> To: Biju Das <biju.das@bp.renesas.com>; Greg Kroah-Hartman
>> <gregkh@linuxfoundation.org>; Rob Herring <robh+dt@kernel.org>; Mark
>> Rutland <mark.rutland@arm.com>
>> Cc: Simon Horman <horms@verge.net.au>; Chris Paterson
>> <Chris.Paterson2@renesas.com>; Fabrizio Castro
>> <fabrizio.castro@bp.renesas.com>; devicetree@vger.kernel.org; linux-renesas-
>> soc@vger.kernel.org; linux-usb@vger.kernel.org; Biju Das
>> <biju.das@bp.renesas.com>
>> Subject: Re: [PATCH] usb: renesas_usbhs: Add compatible string for r8a7743/5
>>
>>
>> Hi,
>>
>> Biju Das <biju.das@bp.renesas.com> writes:
>> > This patch adds support for r8a7743/5 SoC. The Renesas RZ/G1[ME]
>> > (R8A7743/5) usbhs is identical to the R-Car Gen2 family.
>> >
>> > This doesn't change the driver, so it does nothing by itself. But it
>> > does mean that checkpatch won't complain about a future patch that
>> > adds "renesas,usbhs-r8a7743" or "renesas,usbhs-r8a7745" to a DT, which
>> > helps ensure that shipped DTs use documented compatibility strings.
>> >
>> > Signed-off-by: Biju Das <biju.das@bp.renesas.com>
>> > ---
>> > This patch is tested against Linux next tag next-20170929
>
>> care to rebase on my testing/next? It fails to apply.
>
> Sorry for the trouble.
>
> I have already send a V2 for fixing this.
>
> [v2] usb: renesas_usbhs: Add compatible string for r8a7743/5
> https://patchwork.kernel.org/patch/9990063/
>
> I have rebased this patch on my testing/next and confirms it apply cleanly.
thank you, now applied :-)
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-10-17 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 15:12 [PATCH] usb: renesas_usbhs: Add compatible string for r8a7743/5 Biju Das
2017-10-06 2:44 ` Yoshihiro Shimoda
2017-10-06 7:34 ` Geert Uytterhoeven
2017-10-06 8:59 ` Biju Das
2017-10-17 8:25 ` Felipe Balbi
2017-10-17 9:09 ` Biju Das
2017-10-17 9:39 ` Felipe Balbi [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=87fuaijeoq.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro@bp.renesas.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.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