From: Andi Kleen <ak@suse.de>
To: kmannth@us.ibm.com
Cc: lkml <linux-kernel@vger.kernel.org>,
lhms-devel <lhms-devel@lists.sourceforge.net>,
discuss <discuss@x86-64.org>, andrew <akpm@osdl.org>,
dave hansen <haveblue@us.ibm.com>,
kame <kamezawa.hiroyu@jp.fujitsu.com>, konrad <darnok@us.ibm.com>
Subject: Re: [Patch] 1/5 in support of hot-add memory x86_64 nodes_add cleanup
Date: Sat, 29 Jul 2006 21:30:43 +0200 [thread overview]
Message-ID: <200607292130.43189.ak@suse.de> (raw)
In-Reply-To: <1154200962.7900.28.camel@keithlap>
> It was suggested to me in an earlier patch set to move RESERVE_HOTADD to
> Kconfig.
It doesn't make any sense to me.
> I can make it a non-user option. It seems that MEMORY_HOTPLUG
> is a user options so I figured why not make RESERVE one as well. Also I
> don't think people should use reserve with sparsmem.
There should be a single high level Kconfig option for each feature.
-Andi
prev parent reply other threads:[~2006-07-29 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-29 2:52 [Patch] 1/5 in support of hot-add memory x86_64 nodes_add cleanup keith mannthey
2006-07-29 16:24 ` Andi Kleen
2006-07-29 19:22 ` keith mannthey
2006-07-29 19:30 ` Andi Kleen [this message]
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=200607292130.43189.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=darnok@us.ibm.com \
--cc=discuss@x86-64.org \
--cc=haveblue@us.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kmannth@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.