From: Andy Whitcroft <apw@shadowen.org>
To: akpm@osdl.org
Cc: apw@shadowen.org, kravetz@us.ibm.com, haveblue@us.ibm.com,
lhms-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [PATCH 3/4] register_memory should be global
Date: Mon, 14 Nov 2005 19:37:40 +0000 [thread overview]
Message-ID: <20051114193740.GA15501@shadowen.org> (raw)
In-Reply-To: exportbomb.1131997056@pinky
register_memory is global and declared so in linux.h. Update the
HOTPLUG specific definition to match. This fixes a compile warning
when HOTPLUG is enabled.
Signed-off-by: Andy Whitcroft <apw@shadowen.org>
---
memory.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff -upN reference/drivers/base/memory.c current/drivers/base/memory.c
--- reference/drivers/base/memory.c
+++ current/drivers/base/memory.c
@@ -63,8 +63,7 @@ void unregister_memory_notifier(struct n
/*
* register_memory - Setup a sysfs device for a memory block
*/
-static int
-register_memory(struct memory_block *memory, struct mem_section *section,
+int register_memory(struct memory_block *memory, struct mem_section *section,
struct node *root)
{
int error;
next prev parent reply other threads:[~2005-11-14 19:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 19:37 [PATCH 0/4] Squash hotplug warnings Andy Whitcroft
2005-11-14 19:37 ` [PATCH 1/4] __add_section remove unused pgdat definition Andy Whitcroft
2005-11-14 19:37 ` [PATCH 2/4] register_ and unregister_memory_notifier should be global Andy Whitcroft
2005-11-14 23:23 ` Andrew Morton
2005-11-15 0:30 ` mike kravetz
2005-11-15 1:17 ` Andrew Morton
2005-11-14 19:37 ` Andy Whitcroft [this message]
2005-11-14 19:37 ` [PATCH 4/4] memory_hotplug_name should be const Andy Whitcroft
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=20051114193740.GA15501@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=kravetz@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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