From: Peter Horton <pdh@berserk.demon.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19pre5-ac3: unresolved in radeonfb
Date: Sat, 6 Apr 2002 21:30:36 +0100 [thread overview]
Message-ID: <20020406203036.GA503@berserk.demon.co.uk> (raw)
In-Reply-To: <200204051945.g35JjnX23183@devserv.devel.redhat.com> <3CAE3608.8DDE18EB@eyal.emu.id.au>
On Sat, Apr 06, 2002 at 09:40:56AM +1000, Eyal Lebedinsky wrote:
> Alan Cox wrote:
> > Linux 2.4.19pre5-ac3
> > o Small fix for the radeonfb (Peter Horton)
>
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.19-pre5-ac3/kernel/drivers/video/radeonfb.o
> depmod: radeon_engine_init_var
>
> I could not find this symbol in the tree.
>
Darn - I'm not very good at this :-(
Change the call to radeon_engine_init_var() to
radeon_engine_init(rinfo);
P.
next prev parent reply other threads:[~2002-04-06 20:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 19:45 Linux 2.4.19pre5-ac3 Alan Cox
2002-04-05 23:40 ` Linux 2.4.19pre5-ac3: unresolved in radeonfb Eyal Lebedinsky
2002-04-06 20:30 ` Peter Horton [this message]
2002-04-06 1:04 ` Linux 2.4.19pre5-ac3 CaT
2002-04-06 1:09 ` Alan Cox
2002-04-06 1:12 ` CaT
2002-04-07 11:50 ` [swsusp fixes] " Pavel Machek
2002-04-06 17:37 ` Linux 2.4.19pre5-ac3 swsusp panic Ed Sweetman
2002-04-06 18:04 ` Ed Sweetman
2002-04-07 9:58 ` Pavel Machek
[not found] ` <1018546314.32748.9.camel@caffeine.pdx.osdl.net>
[not found] ` <20020412074948.GA26389@atrey.karlin.mff.cuni.cz>
[not found] ` <1018626124.2078.16.camel@caffeine.pdx.osdl.net>
2002-04-14 19:28 ` Pavel Machek
2002-04-06 2:13 ` Linux 2.4.19pre5-ac3 w/swsusp oops brian
2002-04-08 21:46 ` Linux 2.4.19pre5-ac3 Mike Fedyk
2002-04-08 1:38 ` Pavel Machek
[not found] ` <20020409204019.GD523@stingr.net>
2002-04-09 20:53 ` Pavel Machek
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=20020406203036.GA503@berserk.demon.co.uk \
--to=pdh@berserk.demon.co.uk \
--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
all inboxes | Powered by JetHome®