From: Simon Horman <horms@verge.net.au>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: linux-sh@vger.kernel.org, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, devicetree@vger.kernel.org,
magnus.damm@gmail.com, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] Add R8A7794/SILK board PCI USB DT support
Date: Tue, 29 Sep 2015 09:36:00 +0900 [thread overview]
Message-ID: <20150929003600.GA20067@verge.net.au> (raw)
In-Reply-To: <55F4A850.3050806@cogentembedded.com>
Hi Sergei,
On Sun, Sep 13, 2015 at 01:33:52AM +0300, Sergei Shtylyov wrote:
> On 09/13/2015 01:28 AM, Sergei Shtylyov wrote:
>
> > Here's the set of 2 patches against Simon Horman's 'renesas.git' repo's
> >'renesas-devel-20150911v2-v4.2' tag. Here we add PCI USB device tree support
> >for the R8A7794-based SILK board.
>
> Oops, forgot to say that the patches need the 'pci-rcar-gen2' driver
> patch posted yesterday in order to work.
Am I correct in thinking that patch has been accepted and
that therefore I can now pick up this series?
next prev parent reply other threads:[~2015-09-29 0:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-12 22:28 [PATCH 0/2] Add R8A7794/SILK board PCI USB DT support Sergei Shtylyov
2015-09-12 22:30 ` [PATCH 1/2] ARM: shmobile: r8a7794: add internal PCI bridge nodes Sergei Shtylyov
2015-09-12 22:32 ` [PATCH 2/2] ARM: shmobile: silk: enable internal PCI Sergei Shtylyov
[not found] ` <3151312.grtDDBsSl8-gHKXc3Y1Z8zGSmamagVegGFoWSdPRAKMAL8bYrjMMd8@public.gmane.org>
2015-09-12 22:33 ` [PATCH 0/2] Add R8A7794/SILK board PCI USB DT support Sergei Shtylyov
2015-09-29 0:36 ` Simon Horman [this message]
2015-09-29 12:18 ` Sergei Shtylyov
2015-09-30 8:43 ` Simon Horman
2015-10-12 22:12 ` [PATCH] ARM: shmobile: porter: enable internal PCI and USB PHY Sergei Shtylyov
2015-10-13 1:01 ` 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=20150929003600.GA20067@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@cogentembedded.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).