Commit f698a3b5 authored by Paul Gortmaker's avatar Paul Gortmaker Committed by Ralf Baechle

MIPS: SEAD3: Don't use module_init in non-modular sead3-mtd.c code

The sead3-mtd.o is built for obj-y -- and hence this code is always
present.  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.

We also fix a missing semicolon, which this change uncovers.
Signed-off-by: default avatarPaul Gortmaker <paul.gortmaker@windriver.com>
Reported-by: default avatarkbuild test robot <fengguang.wu@intel.com>
Cc: linux-mips@linux-mips.org
Cc: fengguang.wu@intel.com
Patchwork: https://patchwork.linux-mips.org/patch/6412/Signed-off-by: default avatarRalf Baechle <ralf@linux-mips.org>
parent a9dde288
...@@ -50,5 +50,4 @@ static int __init sead3_mtd_init(void) ...@@ -50,5 +50,4 @@ static int __init sead3_mtd_init(void)
return 0; return 0;
} }
device_initcall(sead3_mtd_init);
module_init(sead3_mtd_init)
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment