On Tue, 30 Sep 2008, Linus Torvalds wrote:
It looks like both of these will fall afoul of the fact that ACPI
currently seems to _expect_ to be called in the old order, ie I get some
oops in acpi_irq_penalty_init() apparently because it knew that it got
called later (thanks to being called from pci_acpi_init in the
arch-specific directory), and knew that the other ACPI subsys setup
routines had been done before.
Dang.
I guess we'll have to bite the bullet some day and actually create some
explicit topological ordering of initcalls rather than depend on the
initcall levels and link order. That is one particular complexity I've
tried to avoid. But the subtlety of the current ordering is certainly not
at all good either.
Linus
--
| Greg Kroah-Hartman | [PATCH 008/196] Chinese: add translation of volatile-considered-harmful.txt |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in |
| Andrew Morton | -mm merge plans for 2.6.23 |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Herbert Xu | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Rémi Denis-Courmont | [PATCH 01/14] Phonet global definitions |
