From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] Separate generic header usage from ARCH_MULTIPLATFORM
Date: Fri, 07 Jun 2013 16:04:40 +0200 [thread overview]
Message-ID: <29798869.9FjkuBXpzS@wuerfel> (raw)
In-Reply-To: <3354049.TGIUmJXV0H@wuerfel>
On Friday 07 June 2013 16:00:47 Arnd Bergmann wrote:
> > Doesn't the explicit dependency of CONFIG_MMU for ARCH_MULTIPLATFORM
> > mean that randconfig builds still work, even without the changes below?
> >
> > Apologies if I'm missing a use-case here!
>
> I am somewhat annoyed by the fact that I had to disable ARCH_MULTIPLATFORM
> for !MMU kernels in order to get 'make randconfig' to work and I would rather
> allow it and fix the bugs.
To expand on this a bit more: I want to eventually make ARCH_MULTIPLATFORM
mandatory for all modern platforms, in particular anything ARMv6 and ARMv7
based. Forcing all !MMU-kernels to be !ARCH_MULTIPLATFORM means we won't
get there unless we disallow !MMU on modern platforms.
Arnd
next prev parent reply other threads:[~2013-06-07 14:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 10:48 [PATCH v3 0/3] Separate generic header usage from ARCH_MULTIPLATFORM Jonathan Austin
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 [this message]
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=29798869.9FjkuBXpzS@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