devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Biju Das <biju.das@bp.renesas.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	Chris Paterson <chris.paterson2@renesas.com>,
	devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH  0/5] Add USB2.0 Host support
Date: Fri, 1 Sep 2017 10:55:43 +0200	[thread overview]
Message-ID: <20170901085543.GD14918@verge.net.au> (raw)
In-Reply-To: <1504100473-5528-1-git-send-email-biju.das@bp.renesas.com>

On Wed, Aug 30, 2017 at 02:41:08PM +0100, Biju Das wrote:
> Hello,
> 
> This series aims to add USB2.0 Host support on iWave RZ/G1M(r8a7743)
> based board.
> 
> This series has been tested against renesas-dev tag 20170830-v4.13-rc7
> 
> This patch has documentation dependency on below patches
>  * PCI: rcar: Add r8a7743/5 support
> https://patchwork.kernel.org/patch/9919697/
>  * phy: rcar-gen2: Add r8a7743/5 support
> https://patchwork.kernel.org/patch/9919727/

Thanks for the testing and dependency information.

I see that the PCI dependency has been accepted by Bjorn Helgaas.
And the phy dependency is both trivial and has been acked by Rob Herring
so it seems very likely to be accepted.

On the strength of the above I have accepted this series for v4.15.

> 
> Biju Das (5):
>   ARM: dts: r8a7743: Add internal PCI bridge nodes
>   ARM: dts: r8a7743: Add USB PHY DT support
>   ARM: dts: r8a7743: Link PCI USB devices to USB PHY
>   ARM: dts: iwg20d-q7: Enable internal PCI
>   ARM: dts: iwg20d-q7: Enable USB PHY
> 
>  arch/arm/boot/dts/r8a7743-iwg20d-q7.dts | 26 ++++++++++
>  arch/arm/boot/dts/r8a7743.dtsi          | 92 +++++++++++++++++++++++++++++++++
>  2 files changed, 118 insertions(+)
> 
> -- 
> 1.9.1
> 

  parent reply	other threads:[~2017-09-01  8:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30 13:41 [PATCH 0/5] Add USB2.0 Host support Biju Das
2017-08-30 13:41 ` [PATCH 1/5] ARM: dts: r8a7743: Add internal PCI bridge nodes Biju Das
     [not found] ` <1504100473-5528-1-git-send-email-biju.das-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
2017-08-30 13:41   ` [PATCH 2/5] ARM: dts: r8a7743: Add USB PHY DT support Biju Das
2017-08-30 13:41   ` [PATCH 3/5] ARM: dts: r8a7743: Link PCI USB devices to USB PHY Biju Das
2017-08-30 13:41   ` [PATCH 4/5] ARM: dts: iwg20d-q7: Enable internal PCI Biju Das
2017-08-30 13:41   ` [PATCH 5/5] ARM: dts: iwg20d-q7: Enable USB PHY Biju Das
2017-09-01  8:55 ` Simon Horman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-10-09 13:58 [PATCH 0/5] Add USB2.0 Host support Biju Das
     [not found] ` <1507557541-46560-1-git-send-email-biju.das-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
2017-10-12 10:15   ` 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=20170901085543.GD14918@verge.net.au \
    --to=horms@verge.net.au \
    --cc=biju.das@bp.renesas.com \
    --cc=chris.paterson2@renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=magnus.damm@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).