All of lore.kernel.org
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ux500 DT related fixes and platform enhancements
Date: Mon, 11 Feb 2013 08:32:49 +0000	[thread overview]
Message-ID: <20130211083249.GA3469@gmail.com> (raw)
In-Reply-To: <CACRpkdYChVn6RMnbckR0UiPZC+WdqZjWKvMyoPf=oJifCEgAgw@mail.gmail.com>

On Sun, 10 Feb 2013, Linus Walleij wrote:

> On Fri, Feb 8, 2013 at 9:31 AM, Lee Jones <lee.jones@linaro.org> wrote:
> > On Thu, 07 Feb 2013, Linus Walleij wrote:
> >>
> >> OK so what about I pull this branch into my ux500 git and
> >> call it a devicetree branch, and then we can optionally
> >> merge a few of those ARM: ux500: * patches that
> >> was sent for the regulator stuff on top of that as well?
> >
> > There are two reasons why I don't like that idea: 1) As Olof pointed
> > out, a lot of these patches aren't actually DT related, and 2) I
> > really want all of the regulator stuff to stay together. Each of the
> > changes in the platform code are directly dependent on the ones
> > happening in the regulator driver, and visa versa. It would be best if
> > they continued to be taken though Marks tree.
> 
> I understand this and I'm fully aligned for the non-DT parts.
> 
> But I'm worrying about a plethora or merge conflicts
> under arch/arm/boot/dts/*

Oh no, do as you please with these.

> I already pulled some of the pinctrl device tree patches over to
> my Linux-stericsson tree to avoid clashes between ARM SoC
> and pinctrl.
> 
> Rationale: I don't want arch/arm/boot/dts to become the new
> boardfile-type merge-clash point. That will just invoke the
> wrath of the Big Penguin.
> 
> Yours,
> Linus Walleij

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2013-02-11  8:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130131115552.GG5301@gmail.com>
     [not found] ` <20130206135911.GB7519@gmail.com>
2013-02-06 17:48   ` [GIT PULL] ux500 DT related fixes and platform enhancements Olof Johansson
2013-02-06 22:28     ` Linus Walleij
2013-02-07  2:35       ` Chris Ball
     [not found]     ` <CAF2Aj3gaFtPs7gLd3snzVr1a8Px5A_RN1vz=M+U_LZ3MBpyqqw@mail.gmail.com>
2013-02-07 18:54       ` Linus Walleij
2013-02-08  8:31         ` Lee Jones
2013-02-10 15:08           ` Linus Walleij
2013-02-11  8:32             ` Lee Jones [this message]

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=20130211083249.GA3469@gmail.com \
    --to=lee.jones@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.