linux-kernel - Re: [PATCH] memory-hotplug: revert register_page_bootmem_info_node() to empty when platform related code is not implemented

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <50F52EF8.7050605@cn.fujitsu.com>
Date:	Tue, 15 Jan 2013 18:27:04 +0800
From:	Lin Feng <linfeng@...fujitsu.com>
To:	Michal Hocko <mhocko@...e.cz>
CC:	akpm@...ux-foundation.org, linux-mm@...ck.org,
	wency@...fujitsu.com, jiang.liu@...wei.com, laijs@...fujitsu.com,
	isimatu.yasuaki@...fujitsu.com, linux-kernel@...r.kernel.org,
	tangchen@...fujitsu.com
Subject: Re: [PATCH] memory-hotplug: revert register_page_bootmem_info_node()
 to empty when platform related code is not implemented

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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/