Messages in this thread | | | From | Keith Owens <> | Subject | Re: [PATCH] link time error in drivers/mtd (240t13p2) | Date | Sun, 17 Dec 2000 22:54:39 +1100 |
| |
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/
| |