From: Simon Horman <horms@verge.net.au>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: magnus.damm@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 0/3] arm64: dts: renesas: r8a7795: salvator-xs: enable usb 2.0 channel 3
Date: Thu, 27 Jul 2017 17:20:47 +0200 [thread overview]
Message-ID: <20170727152047.GI16143@verge.net.au> (raw)
In-Reply-To: <1501068660-4032-1-git-send-email-yoshihiro.shimoda.uh@renesas.com>
On Wed, Jul 26, 2017 at 08:30:57PM +0900, Yoshihiro Shimoda wrote:
> This patch is based on the renesas-drivers.git /
> renesas-drivers-2017-07-18-v4.13-rc1 tag and
> "pinctrl: sh-pfc: r8a7795: add usb2.0 on R-Car H3 ES2.0" patch set and
> "arm64: dts: renesas: r8a7795: add usb2.0 for R-Car H3 ES2.0" patch set.
>
> Yoshihiro Shimoda (3):
> arm64: dts: renesas: r8a7795: salvator-xs: enable usb2_phy ch3
> arm64: dts: renesas: r8a7795: salvator-xs: enable USB 2.0 channel 3
> arm64: dts: renesas: r8a7795: salvator-xs: enable HSUSB channel 3
Hi Shimoda-san,
I am marking these patches as deferred pending an Ack from Geert
on the pfc changes. I assume that will not happen until after he comes
back from holiday's. Let me know if that is going to be a problem.
next prev parent reply other threads:[~2017-07-27 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 11:30 [PATCH 0/3] arm64: dts: renesas: r8a7795: salvator-xs: enable usb 2.0 channel 3 Yoshihiro Shimoda
2017-07-26 11:30 ` [PATCH 1/3] arm64: dts: renesas: r8a7795: salvator-xs: enable usb2_phy ch3 Yoshihiro Shimoda
2017-07-26 11:30 ` [PATCH 2/3] arm64: dts: renesas: r8a7795: salvator-xs: enable USB 2.0 channel 3 Yoshihiro Shimoda
2017-07-26 11:31 ` [PATCH 3/3] arm64: dts: renesas: r8a7795: salvator-xs: enable HSUSB " Yoshihiro Shimoda
2017-07-27 15:20 ` Simon Horman [this message]
2017-07-28 8:25 ` [PATCH 0/3] arm64: dts: renesas: r8a7795: salvator-xs: enable usb 2.0 " Simon Horman
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=20170727152047.GI16143@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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