public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Olof Johansson <olof@lixom.net>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
	Arnd Bergmann <arnd@arndb.de>,
	arm@kernel.org, Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	boris.brezillon@free-electrons.com, linus.walleij@linaro.org,
	Ludovic Desroches <ludovic.desroches@atmel.com>
Subject: Re: [GIT PULL] at91: cleanup for 3.16 #1
Date: Sat, 17 May 2014 06:22:16 +0200	[thread overview]
Message-ID: <20140517042216.GI29318@piout.net> (raw)
In-Reply-To: <20140516232635.GB6423@quad.lixom.net>

On 16/05/2014 at 16:26:35 -0700, Olof Johansson wrote :
> On Wed, May 07, 2014 at 07:39:35PM +0200, Nicolas Ferre wrote:
> > There is a little conflict with at91-3.16-dt that you already pulled in
> > arm-soc: here is the branch that resolves it:
> > 
> > https://github.com/at91linux/linux-at91/commits/at91-3.16-resolved
> 
> That resolution looks odd. Why is one clock under clocks { } and two of them
> are at the top level? Shouldn't they all be under the clocks subnode?
> 
> I've merged in now with your resolution, but I think this needs revisiting.
> 

Actually, all the clocks should end up at the root, please refer to:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-March/240219.html

I feel that was one of the topics we should have discussed at ELC but we
ended up talking about DT ABI stability instead...

-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2014-05-17  4:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 17:34 [GIT PULL] at91: cleanup for 3.16 #1 Nicolas Ferre
2014-05-07 17:39 ` Nicolas Ferre
2014-05-16 23:26   ` Olof Johansson
2014-05-16 23:31     ` Olof Johansson
2014-05-19 15:10       ` Nicolas Ferre
2014-05-20  4:28         ` Olof Johansson
2014-05-17  4:22     ` Alexandre Belloni [this message]
2014-05-20  4:25       ` Olof Johansson
2014-05-20  4:32         ` 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=20140517042216.GI29318@piout.net \
    --to=alexandre.belloni@free-electrons.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=boris.brezillon@free-electrons.com \
    --cc=linus.walleij@linaro.org \
    --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 \
    --cc=sfr@canb.auug.org.au \
    /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