[PATCH -mm] acpi: fix memory_hotplug externs
- From: "Randy.Dunlap" <rdunlap@xxxxxxxxxxxx>
- Date: Tue, 28 Mar 2006 11:46:55 -0800
From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
Spell CONFIG option correctly so that externs work.
Fixes these warnings:
drivers/acpi/acpi_memhotplug.c:248: warning: implicit declaration of function 'add_memory'
drivers/acpi/acpi_memhotplug.c:312: warning: implicit declaration of function 'remove_memory'
Signed-off-by: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
---
linsrc/linux-2616-mm2/include/linux/memory_hotplug.h | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
--- rddunlap.orig/linsrc/linux-2616-mm2/include/linux/memory_hotplug.h
+++ rddunlap/linsrc/linux-2616-mm2/include/linux/memory_hotplug.h
@@ -105,7 +105,7 @@ static inline int __remove_pages(struct
}
#if defined(CONFIG_MEMORY_HOTPLUG) || defined(CONFIG_ACPI_HOTPLUG_MEMORY) \
- || defined(CONFIG_ACPI_MEMORY_HOTPLUG_MODULE)
+ || defined(CONFIG_ACPI_HOTPLUG_MEMORY_MODULE)
extern int add_memory(u64 start, u64 size);
extern int remove_memory(u64 start, u64 size);
#endif
---
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Prev by Date: How should an application ask for uinput module load?
- Next by Date: RE: [openib-general] InfiniBand 2.6.17 merge plans
- Previous by thread: How should an application ask for uinput module load?
- Next by thread: Re: no more interrupt load balancing
- Index(es):
Relevant Pages
- [PATCH: 001/017]Memory hotplug for new nodes v.4.(Generic code of pgdat alloc)
... This patch adds node-hot-add support to add_memory. ... get the handle of its
memory device, then get _PXM and node id. ... +int add_memory(int nid, u64 start,
u64 end) ... +extern int add_memory; ... (Linux-Kernel) - [PATCH: 001/017](RFC) Memory hotplug for new nodes v.3. (Generic code of pgdat alloc)
... This patch adds node-hot-add support to add_memory. ... get the handle of its
memory device, then get _PXM and node id. ... +int add_memory(int nid, u64 start,
u64 end) ... +extern int add_memory; ... (Linux-Kernel) - Re: [PATCH] fix memory hot remove not configured case.
... arch dependent code around CONFIG_MEMORY_HOTREMOVE is a mess. ... return
ret; ... -int remove_memory(u64 start, u64 size) ... +extern int offline_pages;
... (Linux-Kernel) - [PATCH] fix memory hot remove not configured case.
... arch dependent code around CONFIG_MEMORY_HOTREMOVE is a mess. ... only powerpc
returns -ENOSYS at memory hot remove. ... -int remove_memory(u64 start, u64 size)
... +extern int offline_pages; ... (Linux-Kernel) - [PATCH] x86_64: fix section mismatch warnings
... Fix the following section mismatch warnings on x86_64: ... The warnings
does not show up during a normal build due to kbuild ... -static void nvidia_bugs ...
extern int fallback_aper_order; ... (Linux-Kernel)
