public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-omap@vger.kernel.org
Subject: [PATCH 0/3] omap cleanup for makefile and init_early
Date: Wed, 24 Aug 2011 04:54:28 -0700	[thread overview]
Message-ID: <20110824115048.2985.24230.stgit@kaulin> (raw)

Hi all,

Here are few patches for review to cleanup mach-omap2 for
Makefile and init_early.

The init_early changes will continue the earlier cleanup
efforts of initializing things later on during the boot
and cutting down dependencies.

Regards,

Tony

---

Tony Lindgren (3):
      omap2+: Use Kconfig symbol in Makefile instead of obj-y
      ARM: OMAP: Move omap2_init_common_devices out of init_early
      ARM: OMAP: Introduce SoC specific early_init


 arch/arm/mach-omap2/Makefile               |   76 ++++++++++++----------------
 arch/arm/mach-omap2/board-2430sdp.c        |    9 +--
 arch/arm/mach-omap2/board-3430sdp.c        |    9 +--
 arch/arm/mach-omap2/board-3630sdp.c        |   11 +---
 arch/arm/mach-omap2/board-4430sdp.c        |    9 +--
 arch/arm/mach-omap2/board-am3517crane.c    |    9 +--
 arch/arm/mach-omap2/board-am3517evm.c      |    8 +--
 arch/arm/mach-omap2/board-apollon.c        |    9 +--
 arch/arm/mach-omap2/board-cm-t35.c         |   13 +----
 arch/arm/mach-omap2/board-cm-t3517.c       |    9 +--
 arch/arm/mach-omap2/board-devkit8000.c     |   12 +---
 arch/arm/mach-omap2/board-generic.c        |    2 -
 arch/arm/mach-omap2/board-h4.c             |    9 +--
 arch/arm/mach-omap2/board-igep0020.c       |   13 +----
 arch/arm/mach-omap2/board-ldp.c            |    9 +--
 arch/arm/mach-omap2/board-n8x0.c           |   13 +----
 arch/arm/mach-omap2/board-omap3beagle.c    |    4 +
 arch/arm/mach-omap2/board-omap3evm.c       |    9 +--
 arch/arm/mach-omap2/board-omap3logic.c     |   11 +---
 arch/arm/mach-omap2/board-omap3pandora.c   |   11 +---
 arch/arm/mach-omap2/board-omap3stalker.c   |    9 +--
 arch/arm/mach-omap2/board-omap3touchbook.c |   11 +---
 arch/arm/mach-omap2/board-omap4panda.c     |    9 +--
 arch/arm/mach-omap2/board-overo.c          |   11 +---
 arch/arm/mach-omap2/board-rm680.c          |   17 +++---
 arch/arm/mach-omap2/board-rx51.c           |   17 +++---
 arch/arm/mach-omap2/board-ti8168evm.c      |    9 +--
 arch/arm/mach-omap2/board-zoom.c           |   23 ++++----
 arch/arm/mach-omap2/io.c                   |   40 +++++++++++++++
 arch/arm/plat-omap/include/plat/common.h   |    9 +++
 30 files changed, 164 insertions(+), 246 deletions(-)

-- 
Signature

             reply	other threads:[~2011-08-24 11:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 11:54 Tony Lindgren [this message]
2011-08-24 11:54 ` [PATCH 1/3] omap2+: Use Kconfig symbol in Makefile instead of obj-y Tony Lindgren
2011-08-24 11:54 ` [PATCH 2/3] ARM: OMAP: Move omap2_init_common_devices out of init_early Tony Lindgren
2011-08-24 12:11   ` Cousson, Benoit
2011-08-24 12:18     ` Santosh
2011-08-24 12:20     ` Tony Lindgren
2011-08-24 13:32       ` Tony Lindgren
2011-08-24 11:54 ` [PATCH 3/3] ARM: OMAP: Introduce SoC specific early_init Tony Lindgren
2011-08-24 12:48   ` Igor Grinberg
2011-08-24 13:35     ` Tony Lindgren

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=20110824115048.2985.24230.stgit@kaulin \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.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