From: Keith Owens <kaos@ocs.com.au>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Rasmus Andersen <rasmus@jaquet.dk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] link time error in drivers/mtd (240t13p2)
Date: Sun, 17 Dec 2000 22:54:39 +1100 [thread overview]
Message-ID: <2750.977054079@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sun, 17 Dec 2000 11:39:50 -0000." <Pine.LNX.4.30.0012171134540.14423-100000@imladris.demon.co.uk>
On Sun, 17 Dec 2000 11:39:50 +0000 (GMT),
David Woodhouse <dwmw2@infradead.org> wrote:
>On Sun, 17 Dec 2000, Keith Owens wrote:
>
>> The rest of the kernel already depends totally on these "subtle" issues
>> with link order. Why should mtd be different?
>
>Because I maintain the MTD code and I want it to be. I think the link
>order dependencies are ugly, unnecessary and far more likely to be
>problematic then the alternatives. I'll code an alternative which is
>cleaner than the current code, and Linus can either accept it or not, as
>he sees fit.
Your choice. Just bear in mind that if CONFIG_MODULES=y but mtd
objects are built into the kernel then mtd _must_ have a correct link
order. Consider a config with CONFIG_MODULES=y but every mtd option is
set to 'y', link order is critical. The moment you have two or more
mtd modules built in then you are stuck with link order issues, no
matter what you do. Of course you could invent and maintain your own
unique method for controlling mtd initialisation order ...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-17 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-16 22:07 [PATCH] link time error in drivers/mtd (240t13p2) Rasmus Andersen
2000-12-16 23:15 ` Keith Owens
2000-12-17 10:01 ` David Woodhouse
2000-12-17 10:32 ` Keith Owens
2000-12-17 10:44 ` David Woodhouse
2000-12-17 10:51 ` Keith Owens
2000-12-17 11:39 ` David Woodhouse
2000-12-17 11:54 ` Keith Owens [this message]
2000-12-17 12:04 ` David Woodhouse
2000-12-17 15:20 ` Alan Cox
2000-12-17 16:32 ` Horst von Brand
2000-12-18 7:47 ` Peter Samuelson
2000-12-17 10:27 ` David Woodhouse
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=2750.977054079@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rasmus@jaquet.dk \
/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