From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Mel Gorman <mel@csn.ul.ie>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, hartleys@visionengravers.com,
mcrapet@gmail.com, fred99@carolina.rr.com,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH] Double check memmap is actually valid with a memmap has unexpected holes
Date: Tue, 5 May 2009 09:36:14 +0100 [thread overview]
Message-ID: <20090505083614.GA28688@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20090505082944.GA25904@csn.ul.ie>
On Tue, May 05, 2009 at 09:29:44AM +0100, Mel Gorman wrote:
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index e02b893..6d79051 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -925,10 +925,9 @@ config OABI_COMPAT
> UNPREDICTABLE (in fact it can be predicted that it won't work
> at all). If in doubt say Y.
>
> -config ARCH_FLATMEM_HAS_HOLES
> +config ARCH_HAS_HOLES_MEMORYMODEL
Can we arrange for EP93xx to select this so we don't have it enabled for
everyone.
The other user of this was RPC when it was flatmem only, but since it has
been converted to sparsemem it's no longer an issue there.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-05-05 8:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 8:29 [PATCH] Double check memmap is actually valid with a memmap has unexpected holes Mel Gorman
2009-05-05 8:36 ` Russell King - ARM Linux [this message]
2009-05-05 8:49 ` Mel Gorman
2009-05-13 16:34 ` [PATCH] Double check memmap is actually valid with a memmap has unexpected holes V2 Mel Gorman
2009-05-13 19:48 ` Andrew Morton
2009-05-14 8:39 ` Mel Gorman
2009-05-17 16:27 ` Russell King - ARM Linux
2009-05-05 11:06 ` [PATCH] Double check memmap is actually valid with a memmap has unexpected holes Johannes Weiner
2009-05-06 14:31 ` Mel Gorman
2009-05-06 15:50 ` Johannes Weiner
2009-05-07 5:29 ` Yasunori Goto
2009-05-14 17:02 ` Paul Mundt
2009-05-06 19:20 ` Russell King - ARM Linux
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=20090505083614.GA28688@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=fred99@carolina.rr.com \
--cc=hartleys@visionengravers.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcrapet@gmail.com \
--cc=mel@csn.ul.ie \
/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).