The patch titled mm: allocate section_map for sparse_init (update) has been added to the -mm tree. Its filename is mm-allocate-section_map-for-sparse_init-update.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: mm: allocate section_map for sparse_init (update) From: Yinghai Lu <yhlu.kernel.send@xxxxxxxxx> allocate section_map in bootmem instead of using __initdata. Signed-off-by: Yinghai Lu <yhlu.kernel@xxxxxxxxx> Cc: Andi Kleen <ak@xxxxxxx> Cc: Yasunori Goto <y-goto@xxxxxxxxxxxxxx> Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> Cc: Ingo Molnar <mingo@xxxxxxx> Cc: Christoph Lameter <clameter@xxxxxxx> Cc: Mel Gorman <mel@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/sparse.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff -puN mm/sparse.c~mm-allocate-section_map-for-sparse_init-update mm/sparse.c --- a/mm/sparse.c~mm-allocate-section_map-for-sparse_init-update +++ a/mm/sparse.c @@ -335,8 +335,7 @@ void __init sparse_init(void) usemap); } - for_each_online_node(node) - free_bootmem_node(NODE_DATA(node), __pa(section_map), size); + free_bootmem(__pa(section_map), size); } #ifdef CONFIG_MEMORY_HOTPLUG _ Patches currently in -mm which might be from yhlu.kernel.send@xxxxxxxxx are origin.patch mm-allocate-section_map-for-sparse_init-update.patch mm-offset-align-in-alloc_bootmem-v3.patch mm-make-reserve_bootmem-can-crossed-the-nodes-v2.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html