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: Thu, 07 Apr 2005 08:30:24 -0700 [thread overview]
Message-ID: <1112887825.14584.59.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.61.0504070219160.15339@scrub.home>
On Thu, 2005-04-07 at 02:30 +0200, Roman Zippel wrote:
> I was hoping for this too, in the meantime can't you simply make it a
> suboption of DISCONTIGMEM? So an extra option is only visible when it's
> enabled and most people can ignore it completely by just disabling a
> single option.
That's reasonable, except that SPARSEMEM doesn't strictly have anything
to do with DISCONTIG.
How about a menu that's hidden under CONFIG_EXPERIMENTAL?
> > I'm not opposed to creating some better help text for those things, I'm
> > just not sure that we really need it, or that it will help end users get
> > to the right place. I guess more explanation never hurt anyone.
>
> Some basic explanation with a link for more information can't hurt.
I'll see what I can come up with.
-- 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-07 15:30 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
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 [this message]
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=1112887825.14584.59.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