From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Olof Johansson <olof@lixom.net>,
arm@kernel.org, Linux Kernel list <linux-kernel@vger.kernel.org>,
"linux-arm-kernel" <linux-arm-kernel@lists.infradead.org>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Boris BREZILLON <boris.brezillon@free-electrons.com>,
"Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@jcrosoft.com>,
Ludovic Desroches <ludovic.desroches@atmel.com>
Subject: Re: [GIT PULL] at91: DT for 3.16 at91-dt3 #3
Date: Fri, 23 May 2014 23:27:51 +0200 [thread overview]
Message-ID: <201405232327.52312.arnd@arndb.de> (raw)
In-Reply-To: <1400775895-31183-1-git-send-email-nicolas.ferre@atmel.com>
On Thursday 22 May 2014, Nicolas Ferre wrote:
> Another AT91 DT pull-request for 3.16. This one is the conversion of two more
> SoC to Common Clock Framework (aka CCF). I identified it as a "DT" pull-request
> but it modifies slightly a couple of files in mach-at91 (use of a configuration
> option).
Four done, four more to go? Nice progress!
> This pull-request depends on:
> - the fixes that I already sent for 3.15 and that are present in the recent
> 3.15-rc6 tag.
> - the at91-cleanup tag that you integrated in your arm-soc/next/soc branch.
> So, as suggested by Arnd on IRC, I merged both of them to act as the base
> before adding the material for this pull-request.
>
> About the clock nodes that should be grouped in a "clocks" container or not,
> while waiting for a clear statement by the DT maintainers, I kept the clocks
> nodes as they had been written by Boris.
> As proposed by Olof, I plan to send you a comprehensive patch that fixes this
> when Mark gives his point of view.
Ok. I've merged it into next/dt now.
Arnd
next prev parent reply other threads:[~2014-05-23 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 16:24 [GIT PULL] at91: DT for 3.16 at91-dt3 #3 Nicolas Ferre
2014-05-23 21:27 ` Arnd Bergmann [this message]
2014-05-23 21:55 ` Alexandre Belloni
2014-05-23 22:01 ` Olof Johansson
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=201405232327.52312.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=alexandre.belloni@free-electrons.com \
--cc=arm@kernel.org \
--cc=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.com \
--cc=olof@lixom.net \
--cc=plagnioj@jcrosoft.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).