summaryrefslogtreecommitdiffstats
path: root/drivers/ata
diff options
context:
space:
mode:
authorBrian King <brking@us.ibm.com>2006-11-13 16:32:36 -0600
committerLinus Torvalds <torvalds@woody.osdl.org>2006-11-14 15:08:50 -0800
commita4625085445b86951d8482c0cdd6d52719f7c323 (patch)
tree0bace40f042c3116ab8a67b0ef2f24e59af995e2 /drivers/ata
parentcb07c9a1864a8eac9f3123e428100d5b2a16e65a (diff)
downloadop-kernel-dev-a4625085445b86951d8482c0cdd6d52719f7c323.zip
op-kernel-dev-a4625085445b86951d8482c0cdd6d52719f7c323.tar.gz
[PATCH] libata: Convert from module_init to subsys_initcall
When building a monolithic kernel, the load order of drivers does not work for SAS libata users, resulting in a kernel oops. Convert libata to use subsys_initcall instead of module_init, which ensures that libata gets loaded before any LLDD. This is the same thing that scsi core does to solve the problem. The load order problem was observed on ipr SAS adapters and should exist for other SAS users as well. Signed-off-by: Brian King <brking@us.ibm.com> Acked-by: Jeff Garzik <jgarzik@pobox.com> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'drivers/ata')
-rw-r--r--drivers/ata/libata-core.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index a8fd0c3..915a55a 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -5957,7 +5957,7 @@ static void __exit ata_exit(void)
destroy_workqueue(ata_aux_wq);
}
-module_init(ata_init);
+subsys_initcall(ata_init);
module_exit(ata_exit);
static unsigned long ratelimit_time;
OpenPOWER on IntegriCloud