All of lore.kernel.org
 help / color / mirror / Atom feed
From: A Guy Called Tyketto <tyketto@wizard.com>
To: linux-kernel@vger.kernel.org
Subject: more unresolved symbols in 2.5.6
Date: Tue, 12 Mar 2002 16:19:57 -0800	[thread overview]
Message-ID: <20020313001957.GA9853@wizard.com> (raw)


        Just going through the rest of the reports in my rolling of 2.5.6.

        With CONFIG_BLK_DEV_IDECD=m, /sbin/depmod -ae -F System.map 2.5.6 from 
make modules_install comes back with:

depmod: *** Unresolved symbols in /lib/modules/2.5.6/kernel/drivers/ide/ide-cd.o
depmod:         ide_fops
depmod: *** Unresolved symbols in /lib/modules/2.5.6/kernel/drivers/net/tulip/de4x5.o
depmod:         virt_to_bus_not_defined_use_pci_map
depmod: *** Unresolved symbols in /lib/modules/2.5.6/kernel/sound/oss/sound.o
depmod:         virt_to_bus_not_defined_use_pci_map

        The virt_to_bus_not_defined_use_pci_map is known and is being worked 
on, AFAIK, but ide_fops is new. Poking around ide-cd.c, line 2514, is the only 
reference to it, inside a devfs_register() call. Leads me to assume that this 
would only show up, if CONFIG_DEVFS_FS is set to Y. Richard, any insights into 
this one? It looks like ide_fops may only need to be exported via ksyms.c, but 
I'd rather have a second opinion..

                                                        BL.
-- 
Brad Littlejohn                         | Email:        tyketto@wizard.com
Unix Systems Administrator,             |           tyketto@ozemail.com.au
Web + NewsMaster, BOFH.. Smeghead! :)   |   http://www.wizard.com/~tyketto
  PGP: 1024D/E319F0BF 6980 AAD6 7329 E9E6 D569  F620 C819 199A E319 F0BF


                 reply	other threads:[~2002-03-13  0:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020313001957.GA9853@wizard.com \
    --to=tyketto@wizard.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.