Commit:     26074962e8f547b96614dbe248748ba2a1996ca3
Parent:     1a632f8cdc33e7f8edca352164f0c96a75d08f08
Author:     Nicolas Pitre <[EMAIL PROTECTED]>
AuthorDate: Sat Jun 16 02:07:53 2007 -0400
Committer:  Pierre Ossman <[EMAIL PROTECTED]>
CommitDate: Sun Sep 23 20:45:39 2007 +0200

    mmc: initialize mmc subsystem with subsys_initcall()
    The problem is that the sdio_bus must be registered before any SDIO
    drivers are registered against it otherwise the kernel sulks.  Because
    the sdio_bus registration happens through module_init (equivalent to
    device_initcall), then any SDIO
    drivers linked before the SDIO core code in the kernel will be initialized
    Upcoming SDIO function drivers are likely to be located outside the
    drivers/mmc directory as it is common practice to group drivers according
    to their function rather than the bus they use.  SDIO drivers are therefore
    likely to appear at random location in the kernel link.
    To make sure the sdio_bus is always initialized before any SDIO drivers,
    let's move the MMC init to the subsys_initcall level.
    Signed-off-by: Nicolas Pitre <[EMAIL PROTECTED]>
    Signed-off-by: Pierre Ossman <[EMAIL PROTECTED]>
 drivers/mmc/core/core.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
index 9747455..b8f27e5 100644
--- a/drivers/mmc/core/core.c
+++ b/drivers/mmc/core/core.c
@@ -771,7 +771,7 @@ static void __exit mmc_exit(void)
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to