archive mirror
 help / color / mirror / Atom feed
From: Marc-Christian Petersen <>
To: Andrea Arcangeli <>, Eyal Lebedinsky <>
Subject: Re: 2.4.22pre7aa1: unresolved in sk98lin
Date: Tue, 2 Sep 2003 09:20:08 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20030901234600.GA11503@dualathlon.random>

On Tuesday 02 September 2003 01:46, Andrea Arcangeli wrote:

Hi Andrea,

> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.22-pre7-aa1/kernel/drivers/net/sk98lin/sk98lin.o
> > depmod:         __udivdi3
> There are several functions triggering this problem, and it's a mainline
> 2.4 problem (I don't see anything specific to my tree).
> I'm CCing the authors of the driver, is there a new version or are we the
> first triggering it? I can fix it myself but I'd prefer to avoid any
> duplication since it's not a one liner.

the problem is _was_ the sk98lin driver, but this problem is gone for a very 
long time now. 2.4.23-pre* will get an update in the next days with sk98lin 
v6.17 (current 6.02 is in mainline) and the problem is gone with it.

Or at least, I don't get the unresolved symbols problem with it ;)

ciao, Marc

  reply	other threads:[~2003-09-02  7:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-19  1:32 2.4.22pre7aa1 Andrea Arcangeli
2003-07-19  8:27 ` 2.4.22pre7aa1 Christoph Hellwig
2003-07-20  8:25 ` 2.4.22pre7aa1: net/bluetooth/cmtp/core.c failure Eyal Lebedinsky
2003-07-21 21:57   ` Marcel Holtmann
2003-07-21 23:24 ` 2.4.22pre7aa1: unresolved in sk98lin Eyal Lebedinsky
2003-09-01 23:46   ` Andrea Arcangeli
2003-09-02  7:20     ` Marc-Christian Petersen [this message]
2003-09-02 15:09       ` Martin Schlemmer
2003-09-02 15:22         ` Andrea Arcangeli
2003-09-02  1:03 Xose Vazquez Perez
2003-09-02  1:09 ` Andrea Arcangeli
2003-09-02  1:43   ` Xose Vazquez Perez
2003-09-02  2:07     ` Andrea Arcangeli

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).