public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Ed Tomlinson <tomlins@cam.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.7-pre5 missing symbols?
Date: Tue, 10 Jul 2001 08:18:10 -0400	[thread overview]
Message-ID: <3B4AF282.A5EA4FA2@mandrakesoft.com> (raw)
In-Reply-To: <20010710115400.5ED711C495@oscar.casa.dyndns.org>

Ed Tomlinson wrote:
> Is it just me or is there something missing?
> 
> oscar# depmod -ae 2.4.7-pre5
> depmod: *** Unresolved symbols in /lib/modules/2.4.7-pre5/kernel/drivers/net/8139too.o
> depmod:         cpu_raise_softirq
> depmod: *** Unresolved symbols in /lib/modules/2.4.7-pre5/kernel/drivers/net/ppp_generic.o
> depmod:         cpu_raise_softirq
> depmod: *** Unresolved symbols in /lib/modules/2.4.7-pre5/kernel/drivers/net/tulip/tulip.o
> depmod:         cpu_raise_softirq
> depmod: *** Unresolved symbols in /lib/modules/2.4.7-pre5/kernel/drivers/net/via-rhine.o
> depmod:         cpu_raise_softirq

Look like a bad patch, pre5 definitely has the following:

> diff -Naur -X /g/g/lib/dontdiff linux-2.4.7-pre4/kernel/ksyms.c linux-2.4.7-pre5/k
> ernel/ksyms.c
> --- linux-2.4.7-pre4/kernel/ksyms.c     Mon Jul  9 23:11:59 2001
> +++ linux-2.4.7-pre5/kernel/ksyms.c     Tue Jul 10 02:00:58 2001
> @@ -538,6 +538,8 @@
>  EXPORT_SYMBOL(tasklet_kill);
>  EXPORT_SYMBOL(__run_task_queue);
>  EXPORT_SYMBOL(do_softirq);
> +EXPORT_SYMBOL(raise_softirq);
> +EXPORT_SYMBOL(cpu_raise_softirq);
>  EXPORT_SYMBOL(tasklet_schedule);
>  EXPORT_SYMBOL(tasklet_hi_schedule);
>  

-- 
Jeff Garzik      | A recent study has shown that too much soup
Building 1024    | can cause malaise in laboratory mice.
MandrakeSoft     |

  reply	other threads:[~2001-07-10 12:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-10 11:53 2.4.7-pre5 missing symbols? Ed Tomlinson
2001-07-10 12:18 ` Jeff Garzik [this message]
2001-07-11  3:54 ` Keith Owens

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=3B4AF282.A5EA4FA2@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomlins@cam.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