Re: [PATCH 2/3] mem-hotplug: Put kernel_physical_mapping_remove() declaration in CONFIG_MEMORY_HOTREMOVE.

2013-04-16 Thread Andrew Morton
On Mon, 15 Apr 2013 17:46:46 +0800 Tang Chen wrote: > kernel_physical_mapping_remove() is only called by arch_remove_memory() in > init_64.c, which is enclosed in CONFIG_MEMORY_HOTREMOVE. So when we don't > configure CONFIG_MEMORY_HOTREMOVE, the compiler will give a warning: > > warning:

Re: [PATCH 2/3] mem-hotplug: Put kernel_physical_mapping_remove() declaration in CONFIG_MEMORY_HOTREMOVE.

2013-04-16 Thread Andrew Morton
On Mon, 15 Apr 2013 17:46:46 +0800 Tang Chen tangc...@cn.fujitsu.com wrote: kernel_physical_mapping_remove() is only called by arch_remove_memory() in init_64.c, which is enclosed in CONFIG_MEMORY_HOTREMOVE. So when we don't configure CONFIG_MEMORY_HOTREMOVE, the compiler will give a warning:

[PATCH 2/3] mem-hotplug: Put kernel_physical_mapping_remove() declaration in CONFIG_MEMORY_HOTREMOVE.

2013-04-15 Thread Tang Chen
kernel_physical_mapping_remove() is only called by arch_remove_memory() in init_64.c, which is enclosed in CONFIG_MEMORY_HOTREMOVE. So when we don't configure CONFIG_MEMORY_HOTREMOVE, the compiler will give a warning: warning: ‘kernel_physical_mapping_remove’ defined but not used So put

[PATCH 2/3] mem-hotplug: Put kernel_physical_mapping_remove() declaration in CONFIG_MEMORY_HOTREMOVE.

2013-04-15 Thread Tang Chen
kernel_physical_mapping_remove() is only called by arch_remove_memory() in init_64.c, which is enclosed in CONFIG_MEMORY_HOTREMOVE. So when we don't configure CONFIG_MEMORY_HOTREMOVE, the compiler will give a warning: warning: ‘kernel_physical_mapping_remove’ defined but not used So put