From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ARM: Remove redundant ARCH_SPARSEMEM_DEFAULT setting
Date: Fri, 05 Jun 2015 14:23:30 +0200 [thread overview]
Message-ID: <2541002.3d7fzEFzRU@wuerfel> (raw)
In-Reply-To: <1433469518-8472-3-git-send-email-gregory.0xf0@gmail.com>
On Thursday 04 June 2015 18:58:37 Gregory Fong wrote:
> From: Kevin Cernekee <cernekee@gmail.com>
>
> If ARCH_SPARSEMEM_ENABLE=y and ARCH_{FLATMEM,DISCONTIGMEM}_ENABLE=n,
> then the logic in mm/Kconfig already makes CONFIG_SPARSEMEM the only
> choice. This is true for all of the existing ARM users of
> ARCH_SPARSEMEM_ENABLE.
>
> Forcing ARCH_SPARSEMEM_DEFAULT=y if ARCH_SPARSEMEM_ENABLE=y prevents
> us from ever defaulting to FLATMEM, so we should remove this setting.
>
> Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
> Signed-off-by: Gregory Fong <gregory.0xf0@gmail.com>
>
Acked-by: Arnd Bergmann <arnd@arndb.de>
It took me a while to understand the logic, but your patch does
make a lot of sense to me now.
Arnd
next prev parent reply other threads:[~2015-06-05 12:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 1:58 [PATCH 0/3] ARM: Allow SPARSEMEM on multiplatform build Gregory Fong
2015-06-05 1:58 ` [PATCH 1/3] ARM: Add default SPARSEMEM settings Gregory Fong
2015-06-05 1:58 ` [PATCH 2/3] ARM: Remove redundant ARCH_SPARSEMEM_DEFAULT setting Gregory Fong
2015-06-05 12:23 ` Arnd Bergmann [this message]
2015-06-05 1:58 ` [PATCH 3/3] ARM: Allow either FLATMEM or SPARSEMEM on the multiplatform build Gregory Fong
2015-06-05 12:26 ` Arnd Bergmann
2015-06-05 19:27 ` Gregory Fong
2015-06-16 23:08 ` [PATCH 0/3] ARM: Allow SPARSEMEM on " Gregory Fong
2015-06-17 19:00 ` Stephen Boyd
-- strict thread matches above, loose matches on Subject: below --
2014-09-12 2:22 [PATCH 1/3] ARM: Add default SPARSEMEM settings Kevin Cernekee
2014-09-12 2:22 ` [PATCH 2/3] ARM: Remove redundant ARCH_SPARSEMEM_DEFAULT setting Kevin Cernekee
2014-10-31 20:12 ` Gregory Fong
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=2541002.3d7fzEFzRU@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