From: Dave Hansen <haveblue@us.ibm.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Andy Whitcroft <apw@shadowen.org>
Subject: Re: [RFC][PATCH 1/4] create mm/Kconfig for arch-independent memory options
Date: Sat, 26 Mar 2005 13:08:23 -0800 [thread overview]
Message-ID: <1111871303.9691.110.camel@localhost> (raw)
In-Reply-To: <4245CC80.10306@osdl.org>
On Sat, 2005-03-26 at 12:56 -0800, Randy.Dunlap wrote:
> I wasn't trying to catch you, but I've already looked at
> all 4 patches in the series and I still can't find an
> option that is labeled/described as "Sparse Memory"....
> The word "sparse" isn't even in patch 3/4... maybe
> there is something missing?
Nope, you're not missing anything. I'm just a little mixed up. You can
find the actual "Sparse Memory" option in this patch:
http://sr71.net/patches/2.6.12/2.6.12-rc1-mhp2/broken-out/B-sparse-151-add-to-mm-Kconfig.patch
I could easily remove the references to it in the patches that I posted
RFC, but I hoped that they would get in quickly enough that it wouldn't
matter. Also, the help option does say that all of the options probably
won't show up. So, users shouldn't be horribly confused if they don't
see the sparsemem option.
-- 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-03-26 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 21:54 Dave Hansen
2005-03-26 3:00 ` Randy.Dunlap
2005-03-26 19:00 ` Dave Hansen
2005-03-26 20:56 ` Randy.Dunlap
2005-03-26 21:08 ` Dave Hansen [this message]
2005-03-26 21:38 ` Randy.Dunlap
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=1111871303.9691.110.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rddunlap@osdl.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