linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: cleanup for 3.16 #1
Date: Mon, 19 May 2014 21:25:25 -0700	[thread overview]
Message-ID: <20140520042525.GA18956@quad.lixom.net> (raw)
In-Reply-To: <20140517042216.GI29318@piout.net>

[adding Mark]

On Sat, May 17, 2014 at 06:22:16AM +0200, Alexandre Belloni wrote:
> 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...

I'm looking more for consistency than anything else. Having a few in the
root and the few in a subnode certainly indicates that something's wrong.

It's a good thing that we have several DT maintainers to spread the load,
but it's also harder to learn the preferences of the maintainer(s) since
there seems to be variety (some care more about some things than others).

I'm not saying that Mark is wrong, but it's quite possible that someone
else would disagree or not care enough to point it out. The current
practice of having clocks under a subnode is prevalent almost everywhere
in the tree, and this is a mostly new direction set by Mark. It makes
it very hard to figure out what's the best way to do things when there's
less consistency.

Clearly, having clocks grouped in a subnode is common practice already, and
makes some sense from a readability point of view.

Anyway, I'll leave the rest for some DT maintainer to sort out. Please
follow up with patches to switch over to one or the other model no matter
what, please.


-Olof

  reply	other threads:[~2014-05-20  4:25 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
2014-05-20  4:25       ` Olof Johansson [this message]
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=20140520042525.GA18956@quad.lixom.net \
    --to=olof@lixom.net \
    --cc=linux-arm-kernel@lists.infradead.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).