From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
horms@verge.net.au, 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, linux@arm.linux.org.uk,
magnus.damm@gmail.com
Subject: Re: [PATCH v4 0/3] Add R8A7791/Koelsch/Henninger board PCI DT support
Date: Tue, 24 Jun 2014 20:22:24 +0200 [thread overview]
Message-ID: <9076479.78BOG4SjZ9@wuerfel> (raw)
In-Reply-To: <201406242207.32790.sergei.shtylyov@cogentembedded.com>
On Tuesday 24 June 2014 22:07:31 Sergei Shtylyov wrote:
>
> Here's the set of 3 patches against Simon Horman's 'renesas.git' repo,
> 'renesas-devel-v3.16-rc2-20140623' tag. Here we add PCI USB device tree support
> for the R8A7791-based Koelsch and Henninger boards. As the 'pci-rcar-gen2'
> driver device tree support has been merged for 3.16, this patchset can now be
> merged too...
>
> [1/3] ARM: shmobile: r8a7791: add internal PCI bridge nodes
> [2/3] ARM: shmobile: koelsch: enable internal PCI
> [3/3] ARM: shmobile: henninger: enable internal PCI
>
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2014-06-24 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 18:07 [PATCH v4 0/3] Add R8A7791/Koelsch/Henninger board PCI DT support Sergei Shtylyov
2014-06-24 18:10 ` [PATCH v4 1/3] ARM: shmobile: r8a7791: add internal PCI bridge nodes Sergei Shtylyov
[not found] ` <201406242207.32790.sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2014-06-24 18:11 ` [PATCH v4 2/3] ARM: shmobile: koelsch: enable internal PCI Sergei Shtylyov
2014-06-24 18:13 ` [PATCH v4 3/3] ARM: shmobile: henninger: " Sergei Shtylyov
2014-06-24 18:22 ` Arnd Bergmann [this message]
2014-07-07 21:21 ` [PATCH v4 0/3] Add R8A7791/Koelsch/Henninger board PCI DT support Sergei Shtylyov
2014-07-08 9:04 ` 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=9076479.78BOG4SjZ9@wuerfel \
--to=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=horms@verge.net.au \
--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).