mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: linux-kernel@vger.kernel.org
Cc: Eyal Lebedinsky <eyal@eyal.emu.id.au>,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: 2.4.21-pre7 ipmi unresolved
Date: Sun, 6 Apr 2003 13:38:51 +0200	[thread overview]
Message-ID: <200304061336.00896.m.c.p@wolk-project.de> (raw)
In-Reply-To: <3E900F09.18EF30CE@eyal.emu.id.au>

[-- Attachment #1: Type: text/plain, Size: 815 bytes --]

On Sunday 06 April 2003 13:27, Eyal Lebedinsky wrote:

Hi Eyal,

> all modules. With two small patches to get HPT372N and ac97
> to compile.
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.21-pre7/kernel/drivers/char/ipmi/ipmi_msghandler.o
> depmod:         panic_notifier_list
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.21-pre7/kernel/drivers/char/ipmi/ipmi_watchdog.o
> depmod:         panic_notifier_list
> depmod:         panic_timeout
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.21-pre7/kernel/drivers/net/wan/comx.o
> depmod:         proc_get_inode
I've already sent a patch to lkml and Marcelo before -pre7.

See: http://marc.theaimsgroup.com/?l=linux-kernel&m=104879598008705&w=2

At least for the ipmi stuff. For the proc_get_inode stuff use the attached 
one.

ciao, Marc




[-- Attachment #2: comx-driver-compile-1.patch --]
[-- Type: text/x-diff, Size: 258 bytes --]

--- 2.4.19pre8aa2/fs/proc/root.c.~1~	Fri May  3 02:12:18 2002
+++ 2.4.19pre8aa2/fs/proc/root.c	Sat May  4 13:45:30 2002
@@ -145,3 +145,4 @@
 EXPORT_SYMBOL(proc_net);
 EXPORT_SYMBOL(proc_bus);
 EXPORT_SYMBOL(proc_root_driver);
+EXPORT_SYMBOL(proc_get_inode);

      reply	other threads:[~2003-04-06 11:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-06 11:27 Eyal Lebedinsky
2003-04-06 11:38 ` 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=200304061336.00896.m.c.p@wolk-project.de \
    --to=m.c.p@wolk-project.de \
    --cc=eyal@eyal.emu.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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®