From: Keith Owens <kaos@ocs.com.au>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_MODVERSIONS and same named files
Date: Sat, 17 Feb 2001 11:28:56 +1100 [thread overview]
Message-ID: <11429.982369736@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Fri, 16 Feb 2001 08:19:28 PDT." <20010216081928.A2209@opus.bloom.county>
On Fri, 16 Feb 2001 08:19:28 -0700,
Tom Rini <trini@kernel.crashing.org> wrote:
>Hey all. The modversions code has a slight problem with files of the same
>name, but in different directories. eg: drivers/a/foo.c exports FOO, and
>drivers/b/foo.c exports BAR, include/linux/modules/foo.ver will only have the
>information about drivers/b/foo.c. Anyone got an idea on how to fix this?
Files that export symbols must have unique names. Which is why we have
abominations like this.
fs/msdos/msdosfs_syms.c
fs/proc/procfs_syms.c
fs/fat/fatfs_syms.c
fs/vfat/vfatfs_syms.c
fs/lockd/lockd_syms.c
kernel/ksyms.c
net/netsyms.c
net/sunrpc/sunrpc_syms.c
net/irda/irsyms.c
Module symbol versions is being completely redesigned for 2.5 and will
not have this problem. In the meantime create a unique filename for
anything that exports symbols.
prev parent reply other threads:[~2001-02-17 0:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 15:19 CONFIG_MODVERSIONS and same named files Tom Rini
2001-02-17 0:28 ` Keith Owens [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=11429.982369736@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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