From: Scott Anderson <scott_anderson@mvista.com>
To: linux-mtd@lists.infradead.org
Subject: cmdline.c file name collision
Date: Tue, 12 Nov 2002 09:46:44 -0800 [thread overview]
Message-ID: <3DD13E84.5B38836C@mvista.com> (raw)
Hi all,
I recently noticed that when CONFIG_MODVERSIONS is turned on, both
drivers/mtd/cmdline.c and lib/cmdline.c are trying to store their
symbol versions in include/linux/modules/cmdline.ver in a 2.4 kernel
tree. Only one of them "wins" leaving the versioned symbols of the
other undefined. It seems to me that drivers/mtd/cmdline.c should
probably be renamed to avoid the conflict. Thoughts?
Scott Anderson
scott_anderson@mvista.com MontaVista Software Inc.
(408)328-9214 1237 East Arques Ave.
http://www.mvista.com Sunnyvale, CA 94085
next reply other threads:[~2002-11-12 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 17:46 Scott Anderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-13 15:25 cmdline.c file name collision Hicks, Jamey
2002-11-13 19:31 ` Scott Anderson
2002-11-14 22:39 Hicks, Jamey
2002-11-15 9:56 ` Robert Kaiser
2002-11-15 10:34 ` Frank Neuber
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=3DD13E84.5B38836C@mvista.com \
--to=scott_anderson@mvista.com \
--cc=linux-mtd@lists.infradead.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