From: Scott Anderson <scott_anderson@mvista.com>
To: "Hicks, Jamey" <Jamey.Hicks@hp.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: cmdline.c file name collision
Date: Wed, 13 Nov 2002 11:31:43 -0800 [thread overview]
Message-ID: <3DD2A89F.BE82BB11@mvista.com> (raw)
In-Reply-To: D99C1FB421989A40818B6370E3187094040A3AB6@tayexc19.americas.cpqcorp.net
"Hicks, Jamey" wrote:
> hmm. My first thought was to rename drivers/mtd/cmdline.c to
> drivers/mtd/mtdcmdline.c or drivers/mtd/cmdlinepart.c.
That sounds reasonable. Does someone that has direct access to the CVS
repository want to move the files around in the repository (so we don't
lose history) or should I just submit a patch that removes the file and
adds the file back with a different name?
> Actually, that was my second thought. My first thought was to wonder
> why CONFIG_MODVERSIONS flattens the kernel source file namespace.
> I just turned on CONFIG_MODVERSIONS to build an ipaq kernel, and I find
> I also have a name conflict on arch/arm/mach-sa1100/pm.c and kernel/pm.c.
I've been told third hand or so that it is a "known limitation" in 2.4.
I just looked in 2.5, and this limitation has been eliminated (there is
a hierarchy of files under include/linux/modules that parallels the
source hierarchy).
With that new found information, I guess a new question comes up: does
working around the 2.4 limitation warrant the rename when the limitation
is removed in 2.5?
Scott Anderson
scott_anderson@mvista.com MontaVista Software Inc.
(408)328-9214 1237 East Arques Ave.
http://www.mvista.com Sunnyvale, CA 94085
next prev parent reply other threads:[~2002-11-13 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 15:25 cmdline.c file name collision Hicks, Jamey
2002-11-13 19:31 ` Scott Anderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-14 22:39 Hicks, Jamey
2002-11-15 9:56 ` Robert Kaiser
2002-11-15 10:34 ` Frank Neuber
2002-11-12 17:46 Scott Anderson
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=3DD2A89F.BE82BB11@mvista.com \
--to=scott_anderson@mvista.com \
--cc=Jamey.Hicks@hp.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 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.