From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: bunk@fs.tum.de, Corey Minyard <minyard@mvista.com>
Cc: linux-kernel@vger.kernel.org, Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: 2.4.21-pre6: IPMI unresolved symbols
Date: Thu, 27 Mar 2003 21:08:35 +0100 [thread overview]
Message-ID: <200303272108.35214.m.c.p@wolk-project.de> (raw)
In-Reply-To: <20030327200401.GX24744@fs.tum.de>
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
On Thursday 27 March 2003 21:04, bunk@fs.tum.de wrote:
Hi Adrian,
> panic_notifier_list and panic_timeout are not EXPORT_SYMBOL'ed in
> kernel/panic.c resulting in the following unresolved symbol errors when
> building IPMI modular:
> <-- snip -->
> ...
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.21-pre6/kernel/drivers/char/ipmi/ipmi_msghandler.o depmod:
> panic_notifier_list
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.21-pre6/kernel/drivers/char/ipmi/ipmi_watchdog.o depmod:
> panic_notifier_list
> depmod: panic_timeout
> ...
patch attached.
ciao, Marc
[-- Attachment #2: ipmi-exported-symbols-fix.patch --]
[-- Type: text/x-diff, Size: 583 bytes --]
--- linux.orig/kernel/ksyms.c Fri Dec 6 09:12:07 2002
+++ linux/kernel/ksyms.c Fri Dec 6 09:13:01 2002
@@ -65,6 +65,8 @@
extern int request_dma(unsigned int dmanr, char * deviceID);
extern void free_dma(unsigned int dmanr);
extern spinlock_t dma_spin_lock;
+extern int panic_timeout;
+
#ifdef CONFIG_MODVERSIONS
const struct module_symbol __export_Using_Versions
@@ -471,6 +471,8 @@
/* misc */
EXPORT_SYMBOL(panic);
+EXPORT_SYMBOL(panic_notifier_list);
+EXPORT_SYMBOL(panic_timeout);
EXPORT_SYMBOL(__out_of_line_bug);
EXPORT_SYMBOL(sprintf);
EXPORT_SYMBOL(snprintf);
prev parent reply other threads:[~2003-03-27 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 20:04 bunk
2003-03-27 20:08 ` Marc-Christian Petersen [this message]
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=200303272108.35214.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=minyard@mvista.com \
/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®