From: Simon Horman <horms@verge.net.au>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: linux-sh@vger.kernel.org, magnus.damm@gmail.com,
linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
rob.herring@calxeda.com, pawel.moll@arm.com,
mark.rutland@arm.com, swarren@wwwdotorg.org,
ian.campbell@citrix.com, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/4] Add Ether DT support for R8A7778/BOCK-W reference board
Date: Mon, 9 Sep 2013 09:11:21 +0900 [thread overview]
Message-ID: <20130909001121.GC21921@verge.net.au> (raw)
In-Reply-To: <201309070423.30672.sergei.shtylyov@cogentembedded.com>
On Sat, Sep 07, 2013 at 04:23:29AM +0400, Sergei Shtylyov wrote:
> Hello.
>
> Here's the set of 4 patches against Simon Horman's 'renesas.git' repo,
> 'renesas-devel-20130906' tag. Here we add the Ether device tree support working
> on the R8A7778/BOCK-W reference board. The patchset requires the 'sh_eth' driver
> device tree support posted earlier in order to work.
These patches seem fine to me.
Magnus, Morimoto-san, do you have any feedback?
Assuming that is a run-time dependency I think I can go ahead
and queue these up for v3.13 once they are reviewed.
>
> [1/4] ARM: shmobile: r8a7778: add Ether DT support
> [2/4] ARM: shmobile: r8a7778: add Ether clock for DT case
> [3/4] ARM: shmobile: bockw-reference: add Ether DT support
> [4/4] ARM: shmobile: BOCK-W reference: add Ether PFC settings
>
> WBR, Sergei
>
next prev parent reply other threads:[~2013-09-09 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 0:23 [PATCH v2 0/4] Add Ether DT support for R8A7778/BOCK-W reference board Sergei Shtylyov
2013-09-07 0:26 ` [PATCH v2 1/4] ARM: shmobile: r8a7778: add Ether DT support Sergei Shtylyov
2013-09-07 0:29 ` [PATCH v2 3/4] ARM: shmobile: bockw-reference: " Sergei Shtylyov
2013-09-09 0:11 ` Simon Horman [this message]
2013-09-09 0:48 ` [PATCH v2 0/4] Add Ether DT support for R8A7778/BOCK-W reference board Kuninori Morimoto
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=20130909001121.GC21921@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=ian.campbell@citrix.com \
--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=rob.herring@calxeda.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=swarren@wwwdotorg.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).