All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lin Feng <linfeng@cn.fujitsu.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	wency@cn.fujitsu.com, jiang.liu@huawei.com, laijs@cn.fujitsu.com,
	isimatu.yasuaki@jp.fujitsu.com, linux-kernel@vger.kernel.org,
	tangchen@cn.fujitsu.com
Subject: Re: [PATCH] memory-hotplug: revert register_page_bootmem_info_node() to empty when platform related code is not implemented
Date: Tue, 15 Jan 2013 18:27:04 +0800	[thread overview]
Message-ID: <50F52EF8.7050605@cn.fujitsu.com> (raw)
In-Reply-To: <20130114184308.GD5126@dhcp22.suse.cz>

Hi Michal,

I have updated to V2 version according to what you said, would you please take a look 
if it conforms to what you think? 

thanks,
linfeng

On 01/15/2013 02:43 AM, Michal Hocko wrote:
> This is just ugly. Could you please add something like HAVE_BOOTMEM_INFO_NODE
> or something with a bettern name and let CONFIG_MEMORY_HOTPLUG select it
> for supported architectures and configurations (e.g.
> CONFIG_SPARSEMEM_VMEMMAP doesn't need a special arch support, right?).
> These Todo things are just too messy.
> -- 

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Lin Feng <linfeng@cn.fujitsu.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	wency@cn.fujitsu.com, jiang.liu@huawei.com, laijs@cn.fujitsu.com,
	isimatu.yasuaki@jp.fujitsu.com, linux-kernel@vger.kernel.org,
	tangchen@cn.fujitsu.com
Subject: Re: [PATCH] memory-hotplug: revert register_page_bootmem_info_node() to empty when platform related code is not implemented
Date: Tue, 15 Jan 2013 18:27:04 +0800	[thread overview]
Message-ID: <50F52EF8.7050605@cn.fujitsu.com> (raw)
In-Reply-To: <20130114184308.GD5126@dhcp22.suse.cz>

Hi Michal,

I have updated to V2 version according to what you said, would you please take a look 
if it conforms to what you think? 

thanks,
linfeng

On 01/15/2013 02:43 AM, Michal Hocko wrote:
> This is just ugly. Could you please add something like HAVE_BOOTMEM_INFO_NODE
> or something with a bettern name and let CONFIG_MEMORY_HOTPLUG select it
> for supported architectures and configurations (e.g.
> CONFIG_SPARSEMEM_VMEMMAP doesn't need a special arch support, right?).
> These Todo things are just too messy.
> -- 

  reply	other threads:[~2013-01-15 10:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 10:53 [PATCH] memory-hotplug: revert register_page_bootmem_info_node() to empty when platform related code is not implemented Lin Feng
2013-01-14 10:53 ` Lin Feng
2013-01-14 18:43 ` Michal Hocko
2013-01-14 18:43   ` Michal Hocko
2013-01-15 10:27   ` Lin Feng [this message]
2013-01-15 10:27     ` Lin Feng

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=50F52EF8.7050605@cn.fujitsu.com \
    --to=linfeng@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=jiang.liu@huawei.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --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 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.