From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM initial multi-platform support
Date: Thu, 20 Sep 2012 21:58:14 -0700 [thread overview]
Message-ID: <20120921045814.GA30535@quad.lixom.net> (raw)
In-Reply-To: <5053B05C.7070801@gmail.com>
On Fri, Sep 14, 2012 at 05:31:56PM -0500, Rob Herring wrote:
> Arnd, Olof,
>
> Please pull initial multi-platform support. This includes the gpio.h
> clean-up that's needed as well. Hopefully it's early enough we will see
> a few other platforms converted over for 3.7.
>
> There's a few minor changes from the last version I posted:
> - Incorporated Jamie Iles fixes for picoxcell.
> - Removed the now unused vexpress uncompress.h and timex.h
> - Fixed the multiple adding of mach directories for spear and exynos.
> - Fixed orion gpio.h includes breaking dove, kirkwood, and orion5x.
>
> Rob
>
> The following changes since commit 4cbe5a555fa58a79b6ecbb6c531b8bab0650778d:
>
> Linux 3.6-rc4 (2012-09-01 10:39:58 -0700)
>
> are available in the git repository at:
>
> git://sources.calxeda.com/kernel/linux.git tags/multi-platform-for-3.7
>
> for you to fetch changes up to 617276307cd4cdb9a95c77efaa3063695af63aa7:
>
> ARM: vexpress: convert to multi-platform (2012-09-14 12:55:09 -0500)
I pulled in this branch now. I created a new next/multiplatform branch that
contains this branch plus one more patch to sweep new dtb targets and move
them to the common file (will post that patch shortly).
To avoid the worst of the conflicts I ended up basing next/multiplatform on
next/cleanup + next/dt + next/soc.
Note that I have not yet merged in the smp_ops branch (will do final
sync-up with Arnd on that tomorrow), so selecting multiple targets will
fail building due to duplicate symbols.
-Olof
next prev parent reply other threads:[~2012-09-21 4:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 22:31 [GIT PULL] ARM initial multi-platform support Rob Herring
2012-09-21 4:58 ` Olof Johansson [this message]
2012-09-21 13:45 ` Shawn Guo
2012-09-21 14:52 ` Arnd Bergmann
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=20120921045814.GA30535@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 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.