summaryrefslogtreecommitdiffstats
path: root/arch/m68k/mvme16x
diff options
context:
space:
mode:
authorPaul Gortmaker <paul.gortmaker@windriver.com>2014-01-16 17:15:14 -0500
committerGeert Uytterhoeven <geert@linux-m68k.org>2015-01-11 11:38:41 +0100
commit51ad77ada1edc2c4096730820c45756cd8f112ad (patch)
tree66c1b0e1e44a375b1dcb2554c1062f204bf5e0ce /arch/m68k/mvme16x
parentb1940cd21c0f4abdce101253e860feff547291b0 (diff)
downloadlinux-stable-51ad77ada1edc2c4096730820c45756cd8f112ad.tar.gz
linux-stable-51ad77ada1edc2c4096730820c45756cd8f112ad.tar.bz2
linux-stable-51ad77ada1edc2c4096730820c45756cd8f112ad.zip
m68k/mvme16x: rtc - Don't use module_init in non-modular code
The rtc.o is built for obj-y, i.e. always built in. It will never be modular, so using module_init as an alias for __initcall can be somewhat misleading. Fix this up now, so that we can relocate module_init from init.h into module.h in the future. If we don't do this, we'd have to add module.h to obviously non-modular code, and that would be a worse thing. Note that direct use of __initcall is discouraged, vs. one of the priority categorized subgroups. As __initcall gets mapped onto device_initcall, our use of device_initcall directly in this change means that the runtime impact is zero -- it will remain at level 6 in initcall ordering. Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Diffstat (limited to 'arch/m68k/mvme16x')
-rw-r--r--arch/m68k/mvme16x/rtc.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/m68k/mvme16x/rtc.c b/arch/m68k/mvme16x/rtc.c
index 6ef7a81a3b12..1755e2f7137d 100644
--- a/arch/m68k/mvme16x/rtc.c
+++ b/arch/m68k/mvme16x/rtc.c
@@ -161,4 +161,4 @@ static int __init rtc_MK48T08_init(void)
printk(KERN_INFO "MK48T08 Real Time Clock Driver v%s\n", RTC_VERSION);
return misc_register(&rtc_dev);
}
-module_init(rtc_MK48T08_init);
+device_initcall(rtc_MK48T08_init);