linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Tang Chen <tangchen@cn.fujitsu.com>
Cc: akpm@linux-foundation.org, isimatu.yasuaki@jp.fujitsu.com,
	kamezawa.hiroyu@jp.fujitsu.com, mel@csn.ul.ie,
	laijs@cn.fujitsu.com, wency@cn.fujitsu.com, mingo@elte.hu,
	penberg@kernel.org, torvalds@linux-foundation.org,
	linux-mm@kvack.org, 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 03:19:04 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1212170318110.21139@chino.kir.corp.google.com> (raw)
In-Reply-To: <1355708488-2913-3-git-send-email-tangchen@cn.fujitsu.com>

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.

--
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:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-12-17 11:19 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 [this message]
2012-12-17 19:44     ` Linus Torvalds

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=alpine.DEB.2.00.1212170318110.21139@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --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=tangchen@cn.fujitsu.com \
    --cc=torvalds@linux-foundation.org \
    --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