From: Adrian Bunk <bunk@stusta.de>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH -mm] acpi: fix memory_hotplug externs
Date: Sun, 2 Apr 2006 00:16:41 +0200 [thread overview]
Message-ID: <20060401221641.GC11800@stusta.de> (raw)
In-Reply-To: <20060328114655.05e1933f.rdunlap@xenotime.net>
On Tue, Mar 28, 2006 at 11:46:55AM -0800, Randy.Dunlap wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> 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@xenotime.net>
> ---
> 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
What about simply offering the prototypes unconditionally?
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-04-01 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 19:46 [PATCH -mm] acpi: fix memory_hotplug externs Randy.Dunlap
2006-04-01 22:16 ` Adrian Bunk [this message]
2006-04-02 0:08 ` Randy.Dunlap
2006-04-02 8:56 ` [-mm patch] memory_hotplug.h: no need to #if guard the {add,remove}_memory() prototypes Adrian Bunk
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=20060401221641.GC11800@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox