From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Rientjes <rientjes@google.com>
Cc: Pekka Enberg <penberg@kernel.org>,
Tang Chen <tangchen@cn.fujitsu.com>,
linux-mm@kvack.org, wency@cn.fujitsu.com, mel@csn.ul.ie,
mingo@elte.hu, akpm@linux-foundation.org,
kamezawa.hiroyu@jp.fujitsu.com, laijs@cn.fujitsu.com,
isimatu.yasuaki@jp.fujitsu.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] memory-hotplug: Disable CONFIG_MOVABLE_NODE option by default.
Date: Mon, 17 Dec 2012 11:44:36 -0800 [thread overview]
Message-ID: <CA+55aFwuT1aQt5HDTTLjk2HfyTK7jK=SAVxuQZiDfq-yS7D9BA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1212170318110.21139@chino.kir.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
The only thing broken about it was the condign option and the lack of docs,
so...
Linus
On Dec 17, 2012 3:19 AM, "David Rientjes" <rientjes@google.com> wrote:
> On Mon, 17 Dec 2012, Tang Chen wrote:
>
> > This patch set CONFIG_MOVABLE_NODE to "default n" instead of
> > "depends on BROKEN".
> >
> > Signed-off-by: Tang Chen <tangchen@cn.fujitsu.com>
> > Reviewed-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
>
> It's fine to change the default, but what's missing here is a rationale
> for no longer making it depend on CONFIG_BROKEN.
>
[-- Attachment #2: Type: text/html, Size: 999 bytes --]
prev parent reply other threads:[~2012-12-17 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 1:41 [PATCH v2 0/2] Add help info for CONFIG_MOVABLE_NODE and disable is " Tang Chen
2012-12-17 1:41 ` [PATCH v2 1/2] memory-hotplug: Add help info for CONFIG_MOVABLE_NODE option Tang Chen
2012-12-17 1:41 ` [PATCH v2 2/2] memory-hotplug: Disable CONFIG_MOVABLE_NODE option by default Tang Chen
2012-12-17 11:19 ` David Rientjes
2012-12-17 19:44 ` Linus Torvalds [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='CA+55aFwuT1aQt5HDTTLjk2HfyTK7jK=SAVxuQZiDfq-yS7D9BA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=tangchen@cn.fujitsu.com \
--cc=wency@cn.fujitsu.com \
/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