linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jonathan.austin@arm.com (Jonathan Austin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] Separate generic header usage from ARCH_MULTIPLATFORM
Date: Fri,  7 Jun 2013 11:48:28 +0100	[thread overview]
Message-ID: <1370602111-28737-1-git-send-email-jonathan.austin@arm.com> (raw)

The original aim of this series was to restore the ability to build a NOMMU
kernel for Versatile Express, something that was lost when we converted
ARCH_VEXPRESS for ARCH_MULTIPLATFORM.

In order to do this, it is necessary to abstract the use of generic headers
from selection of ARCH_MULTIPLATFORM so that the two can be used separately.
This is necessary becuase building a multiplatform kernel for processors
without and MMU doesn't make sense (it is necessary to hardcode certain mem-map
related data) and the versatile express can host NOMMU processors.

This series performs this separation, and then goes on to add a 'dummy'
ARCH_VEXPRESS_NOMMU platform that can be selected as standalone platform.

Patch 2 was sent to the list as an RFC some time ago where it was ACKd, but
alone is not sufficient to solve the problem, hence this follow-up series.

Changes since V1:
 - Rebase on to 3.10-rc1: fixup conflict from CONFIG_UNCOMPRESS_INCLUDE-foo

Changes since V2
 - Rename ARM_GENERIC_HEADERS to NEED_NO_MACH_HEADERS as suggested/requested by
   Rob Herring

Jonathan Austin (3):
  ARM: allow platforms to use generic headers without
    ARCH_MULTIPLATFORM
  ARM: nommu: re-enable use of vexpress without ARCH_MULTIPLATFORM
  ARM: vexpress-nommu: add a Makefile.boot to restore single-platform
    build

 arch/arm/Kconfig                     |   21 +++++++++++++++++++++
 arch/arm/Kconfig.debug               |    4 ++--
 arch/arm/Makefile                    |    2 +-
 arch/arm/include/asm/timex.h         |    2 +-
 arch/arm/mach-mvebu/Makefile         |    2 +-
 arch/arm/mach-omap2/Makefile         |    2 +-
 arch/arm/mach-vexpress/Makefile      |    2 +-
 arch/arm/mach-vexpress/Makefile.boot |    4 ++++
 arch/arm/plat-omap/Makefile          |    2 +-
 arch/arm/plat-orion/Makefile         |    2 +-
 arch/arm/plat-versatile/Makefile     |    2 +-
 11 files changed, 35 insertions(+), 10 deletions(-)
 create mode 100644 arch/arm/mach-vexpress/Makefile.boot

-- 
1.7.9.5

             reply	other threads:[~2013-06-07 10:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 10:48 Jonathan Austin [this message]
2013-06-07 10:48 ` [PATCH v3 1/3] ARM: allow platforms to use generic headers without ARCH_MULTIPLATFORM Jonathan Austin
2013-06-07 10:48 ` [PATCH v3 2/3] ARM: nommu: re-enable use of vexpress " Jonathan Austin
2013-06-07 10:48 ` [PATCH v3 3/3] ARM: vexpress-nommu: add a Makefile.boot to restore single-platform build Jonathan Austin
2013-06-07 12:36 ` [PATCH v3 0/3] Separate generic header usage from ARCH_MULTIPLATFORM Arnd Bergmann
2013-06-07 13:13   ` Jonathan Austin
2013-06-07 14:00     ` Arnd Bergmann
2013-06-07 14:04       ` Arnd Bergmann
2013-06-07 16:51         ` Jonathan Austin
2013-06-07 17:33           ` Arnd Bergmann
2013-06-07 17:50             ` Jonathan Austin

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=1370602111-28737-1-git-send-email-jonathan.austin@arm.com \
    --to=jonathan.austin@arm.com \
    --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).