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 21:32:24 +1100 [thread overview]
Message-ID: <1875.977049144@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sun, 17 Dec 2000 10:01:07 -0000." <Pine.LNX.4.30.0012170959580.14423-100000@imladris.demon.co.uk>
On Sun, 17 Dec 2000 10:01:07 +0000 (GMT),
David Woodhouse <dwmw2@infradead.org> wrote:
>On Sun, 17 Dec 2000, Keith Owens wrote:
>
>> Somebody changed include/linux/mtd/map.h between 2.4.0-test11 and
>> test12. That change is wrong, it adds conditional complexity where it
>> is not required - inter_module_xxx works even without CONFIG_MODULES.
>> cfi_probe should still be static.
>
>No. Think about the link order. inter_module_xxx doesn't work reliably.
>get_module_symbol() did.
Messing about with conditional compilation because the link order is
incorrect is the wrong fix. The mtd/Makefile must link the objects in
the correct order.
cfi_probe.o needs to come after cfi_cmdset_000?.o.
doc_probe.o needs to come after doc200?.o.
nora.o, octagon-5066.o, physmap.o, rpxlite.o, vmax301.o, pnc2000.o need
to come after cfi_probe.o.
octagon-5066.o, vmax301.o need to come after jedec.o.
octagon-5066.o, vmax301.o need to come after map_ram.o.
octagon-5066.o, vmax301.o need to come after map_rom.o.
2.4.0-test13-pre2 almost does that, the only obvious problem is that
cfi_probe appears before cfi_cmdset. Move cfi_probe to link after
cfi_cmdset, do you still get link order problems with the 2.4.0-test11
version of include/linux/mtd.h?
-
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 11:03 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 [this message]
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
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=1875.977049144@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;
as well as URLs for NNTP newsgroup(s).