From: Dave Hansen <haveblue@us.ibm.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Andy Whitcroft <apw@shadowen.org>
Subject: Re: [PATCH 1/4] create mm/Kconfig for arch-independent memory options
Date: Wed, 06 Apr 2005 14:01:59 -0700 [thread overview]
Message-ID: <1112821319.14584.28.camel@localhost> (raw)
In-Reply-To: <42544D7E.1040907@linux-m68k.org>
On Wed, 2005-04-06 at 22:58 +0200, Roman Zippel wrote:
> Dave Hansen wrote:
> > --- memhotplug/mm/Kconfig~A6-mm-Kconfig 2005-04-04 09:04:48.000000000 -0700
> > +++ memhotplug-dave/mm/Kconfig 2005-04-04 10:15:23.000000000 -0700
> > @@ -0,0 +1,25 @@
> > +choice
> > + prompt "Memory model"
> > + default FLATMEM
> > + default SPARSEMEM if ARCH_SPARSEMEM_DEFAULT
> > + default DISCONTIGMEM if ARCH_DISCONTIGMEM_DEFAULT
>
> Does this really have to be a user visible option and can't it be
> derived from other values? The help text entries are really no help at all.
I hope that this selection will replace the current DISCONTIGMEM prompts
in the individual architectures. That way, you won't get a net increase
in the number of prompts. However, I do realize that architectures
without DISCONTIG see a new, relatively useless menu/prompt.
Is there a way to hide an entire "choice" menu? If there is, we can
certainly hide it when there's only one possible choice.
-- Dave
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-04-06 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 17:50 Dave Hansen
2005-04-04 23:22 ` Mike Kravetz
2005-04-04 23:29 ` Dave Hansen
2005-04-06 20:58 ` Roman Zippel
2005-04-06 21:01 ` Dave Hansen [this message]
2005-04-06 23:40 ` Roman Zippel
2005-04-06 23:57 ` Dave Hansen
2005-04-07 0:30 ` Roman Zippel
2005-04-07 15:30 ` Dave Hansen
2005-04-07 16:36 ` Dave Hansen
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=1112821319.14584.28.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=zippel@linux-m68k.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