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/2] arm64: dts: r8a7796: add USB-DMAC and HSUSB device nodes
Date: Thu, 17 Aug 2017 10:25:42 +0200 [thread overview]
Message-ID: <20170817082542.GC27693@verge.net.au> (raw)
In-Reply-To: <20170804110026.GB9178@verge.net.au>
On Fri, Aug 04, 2017 at 01:00:27PM +0200, Simon Horman wrote:
> On Thu, Aug 03, 2017 at 09:29:15PM +0900, Yoshihiro Shimoda wrote:
> > This patch is based on the renesas.git / renesas-devel-20170731v2-v4.13-rc3 tag.
> >
> > For usb-dmac, we should wait for the following patch (even if we don't apply
> > the patch, the usb-dmac driver can be probed correctly though.)
> > https://patchwork.kernel.org/patch/9876639/
> >
> > For hsusb, we need the "arm64: dts: r8a7796: add usb host device nodes" patch
> > set for using usb2_phy0.
>
> Thanks, I am marking this series as deferred pending acceptance of
> the dependencies of "arm64: dts: r8a7796: add usb host device nodes".
> Please repost this series or otherwise ping me once those
> dependencies are in place.
The dependency is now in place and I have applied this series.
next prev parent reply other threads:[~2017-08-17 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 12:29 [PATCH 0/2] arm64: dts: r8a7796: add USB-DMAC and HSUSB device nodes Yoshihiro Shimoda
[not found] ` <1501763357-26075-1-git-send-email-yoshihiro.shimoda.uh-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2017-08-03 12:29 ` [PATCH 1/2] arm64: dts: r8a7796: Add USB-DMAC " Yoshihiro Shimoda
2017-08-04 11:00 ` [PATCH 0/2] arm64: dts: r8a7796: add USB-DMAC and HSUSB " Simon Horman
2017-08-17 8:25 ` Simon Horman [this message]
2017-08-03 12:29 ` [PATCH 2/2] arm64: dts: r8a7796: Add HSUSB device node Yoshihiro Shimoda
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=20170817082542.GC27693@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;
as well as URLs for NNTP newsgroup(s).