From: Samuel Flory <sflory@rackable.com>
To: Matt Bernstein <matt@theBachChoir.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-pre4-ac1 modular IDE symbol problems
Date: 23 Aug 2002 10:43:29 -0700 [thread overview]
Message-ID: <1030124610.23141.1294.camel@flory.corp.rackablelabs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0208231528560.2524-100000@localhost.localdomain>
This is a know issue in Alan's release notes.
On Fri, 2002-08-23 at 07:30, Matt Bernstein wrote:
> Hope the below is useful (I know not too many people build IDE as modules)
> (built using Red Hat (null))
>
> depmod: *** Unresolved symbols in /lib/modules/2.4.20-pre4-ac1/kernel/drivers/ide/ide-disk.o
> depmod: proc_ide_read_geometry
> depmod: ide_remove_proc_entries
> depmod: *** Unresolved symbols in /lib/modules/2.4.20-pre4-ac1/kernel/drivers/ide/ide-floppy.o
> depmod: proc_ide_read_geometry
> depmod: ide_remove_proc_entries
> depmod: *** Unresolved symbols in /lib/modules/2.4.20-pre4-ac1/kernel/drivers/ide/ide-probe.o
> depmod: do_ide_request
> depmod: ide_add_generic_settings
> depmod: create_proc_ide_interfaces
> depmod: *** Unresolved symbols in /lib/modules/2.4.20-pre4-ac1/kernel/drivers/ide/ide-tape.o
> depmod: ide_remove_proc_entries
> depmod: *** Unresolved symbols in /lib/modules/2.4.20-pre4-ac1/kernel/drivers/ide/ide.o
> depmod: ide_release_dma
> depmod: ide_add_proc_entries
> depmod: ide_scan_pcibus
> depmod: proc_ide_read_capacity
> depmod: proc_ide_create
> depmod: ide_remove_proc_entries
> depmod: destroy_proc_ide_drives
> depmod: proc_ide_destroy
> depmod: create_proc_ide_interfaces
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2002-08-23 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 14:30 Matt Bernstein
2002-08-23 17:43 ` Samuel Flory [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=1030124610.23141.1294.camel@flory.corp.rackablelabs.com \
--to=sflory@rackable.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@theBachChoir.org.uk \
/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®