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, 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
Date: Tue, 17 Oct 2017 11:25:54 +0300 [thread overview]
Message-ID: <87wp3uji3x.fsf@linux.intel.com> (raw)
In-Reply-To: <1507216358-917-1-git-send-email-biju.das@bp.renesas.com>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
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.
While doing that, please collect all Acks given.
8<------------------------------------------------------------------------
checking file Documentation/devicetree/bindings/usb/renesas_usbhs.txt
Hunk #2 FAILED at 12.
1 out of 2 hunks FAILED
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-10-17 8:26 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 [this message]
2017-10-17 9:09 ` Biju Das
2017-10-17 9:39 ` Felipe Balbi
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=87wp3uji3x.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=biju.das@bp.renesas.com \
--cc=chris.paterson2@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