From: Karsten Wiese <fzu@wemgehoertderstaat.de>
To: Marcus Hartig <m.f.h@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc6-rt5
Date: Tue, 21 Nov 2006 13:45:10 +0100 [thread overview]
Message-ID: <200611211345.10983.fzu@wemgehoertderstaat.de> (raw)
In-Reply-To: <4562EAA9.8020102@web.de>
Am Dienstag, 21. November 2006 13:01 schrieb Marcus Hartig:
> HI!
>
> rt4 runs fine. But while compiling 2.6.19-rc6-rt5 I get this error:
>
> CC mm/page_alloc.o
> mm/page_alloc.c: In function 'page_alloc_init':
> mm/page_alloc.c:2793: error: 'page_alloc_cpu_notify' undeclared (first use
> in this function)
> mm/page_alloc.c:2793: error: (Each undeclared identifier is reported only once
> mm/page_alloc.c:2793: error: for each function it appears in.)
> make[1]: *** [mm/page_alloc.o] Error 1
> make: *** [mm] Error 2
Ingo posted a fix in another thread.
The (whitespace damaged, handapply!) excerpt of that fix below made
i386 compile here.
Karsten
Index: linux/mm/page_alloc.c
===================================================================
--- linux.orig/mm/page_alloc.c
+++ linux/mm/page_alloc.c
@@ -2768,7 +2768,6 @@ void __init free_area_init(unsigned long
__pa(PAGE_OFFSET) >> PAGE_SHIFT, NULL);
}
-#ifdef CONFIG_HOTPLUG_CPU
static int page_alloc_cpu_notify(struct notifier_block *self,
unsigned long action, void *hcpu)
{
@@ -2786,7 +2785,6 @@ static int page_alloc_cpu_notify(struct
}
return NOTIFY_OK;
}
-#endif /* CONFIG_HOTPLUG_CPU */
void __init page_alloc_init(void)
{
-
next prev parent reply other threads:[~2006-11-21 12:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 12:01 2.6.19-rc6-rt5 Marcus Hartig
2006-11-21 12:45 ` Karsten Wiese [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-25 22:01 2.6.19-rc6-rt5 Thomas
2006-11-20 22:02 2.6.19-rc6-rt5 Ingo Molnar
2006-11-20 22:39 ` 2.6.19-rc6-rt5 Alistair John Strachan
2006-11-21 7:17 ` 2.6.19-rc6-rt5 Ingo Molnar
2006-11-20 23:18 ` 2.6.19-rc6-rt5 Alistair John Strachan
2006-11-21 7:20 ` 2.6.19-rc6-rt5 Ingo Molnar
2006-11-21 1:35 ` 2.6.19-rc6-rt5 Sergio Monteiro Basto
2006-11-21 8:04 ` 2.6.19-rc6-rt5 Ingo Molnar
2006-11-22 11:37 ` 2.6.19-rc6-rt5 Robert Schwebel
2006-11-23 20:43 ` 2.6.19-rc6-rt5 Eduardo Valentin
2006-11-23 21:11 ` 2.6.19-rc6-rt5 Robert Schwebel
2006-11-22 14:06 ` 2.6.19-rc6-rt5 Mark Knecht
2006-11-28 17:33 ` 2.6.19-rc6-rt5 Lee Revell
2006-11-28 19:53 ` 2.6.19-rc6-rt5 Mark Knecht
2006-11-28 20:16 ` 2.6.19-rc6-rt5 Lee Revell
2006-11-28 20:15 ` 2.6.19-rc6-rt5 Ingo Molnar
2006-11-28 22:52 ` 2.6.19-rc6-rt5 Mark Knecht
2006-11-29 6:54 ` 2.6.19-rc6-rt5 Ingo Molnar
2006-11-26 14:39 ` 2.6.19-rc6-rt5 Karsten Wiese
2006-11-27 7:48 ` 2.6.19-rc6-rt5 Ingo Molnar
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=200611211345.10983.fzu@wemgehoertderstaat.de \
--to=fzu@wemgehoertderstaat.de \
--cc=linux-kernel@vger.kernel.org \
--cc=m.f.h@web.de \
/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
all inboxes | Powered by JetHome®