Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: realview: basic device tree implementation
Date: Thu, 22 May 2014 15:38:14 +0200	[thread overview]
Message-ID: <4386397.P7WlMhNVxk@wuerfel> (raw)
In-Reply-To: <CACRpkdYE0Fb+HezqgDbVcqQmWwn7QL2+RWSRyAigv2qcMp2qFQ@mail.gmail.com>

On Thursday 22 May 2014 15:04:07 Linus Walleij wrote:
> On Thu, May 22, 2014 at 10:31 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Thursday 22 May 2014 09:41:39 Linus Walleij wrote:
> 
> >> The question can be rephrased like this:
> >> Should we create drivers/soc?
> >
> > I think we just did, not sure if the patches have made it into linux-next
> > already, but there were a couple of other platforms already that want this
> > directory.
> 
> Awesomeness. Can you give me the title of a patch or branch
> from ARM SoC I should pull in to build on top of this? Then I can
> split off all the SoC bus business and have the machine file real
> small, nice and clean.

I'd have to check again, it seems that as of today, there is no drivers/soc
on arm-soc yet. I do remember that there were at least two platforms besides
yours that want it though, so we have to coordinate it a bit.

Then again, as I expect all of them to go through arm-soc, we can probably
resolve the conflicts in our tree.

	Arnd

  reply	other threads:[~2014-05-22 13:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 22:08 [PATCH v2] ARM: realview: basic device tree implementation Linus Walleij
2014-05-09 10:44 ` Arnd Bergmann
2014-05-22  7:41   ` Linus Walleij
2014-05-22  8:31     ` Arnd Bergmann
2014-05-22 13:04       ` Linus Walleij
2014-05-22 13:38         ` Arnd Bergmann [this message]
2014-05-22 14:45       ` Catalin Marinas
2014-05-22 15:49         ` Arnd Bergmann
2014-05-22 16:09           ` Catalin Marinas
2014-05-22 18:09           ` Nicolas Pitre
2014-05-22 18:26             ` Arnd Bergmann
2014-05-22 18:39               ` Nicolas Pitre
2014-05-22 20:25                 ` Arnd Bergmann
2014-05-22 18:52           ` Linus Walleij
2014-05-22 20:35             ` Arnd Bergmann
2014-05-29  9:38               ` Linus Walleij
2014-05-22 22:34     ` Sebastian Hesselbarth
2014-05-29  9:44       ` Linus Walleij
2014-05-29 10:10         ` Sebastian Hesselbarth
2014-05-29 14:13           ` Linus Walleij
2014-05-29 14:47             ` Sebastian Hesselbarth
2014-05-22 13:17 ` Rob Herring
2014-05-22 13:30   ` Linus Walleij
2014-05-22 13:36     ` Arnd Bergmann
2014-05-22 13:41 ` Jason Cooper

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=4386397.P7WlMhNVxk@wuerfel \
    --to=arnd@arndb.de \
    --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