linux/arch/cris
Paul Gortmaker 84c3e5bf1d cris: don't use module_init for non-modular core eeprom.c code
The eeprom.c code is compiled based on the Kconfig setting
ETRAX_I2C_EEPROM, which is bool.  So the code is either built in
or absent.  It will never be modular, so using module_init as an
alias for __initcall is rather 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.

Direct use of __initcall is discouraged, vs prioritized ones.
Use of device_initcall is consistent with what __initcall
maps onto, and hence does not change the init order, making the
impact of this change zero.   Should someone with real hardware
for boot testing want to change it later to arch_initcall or
something different, they can do that at a later date.

Cc: Mikael Starvik <starvik@axis.com>
Cc: Jesper Nilsson <jesper.nilsson@axis.com>
Cc: linux-cris-kernel@axis.com
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
2015-06-16 14:12:31 -04:00
..
arch-v10 cris: don't use module_init for non-modular core eeprom.c code 2015-06-16 14:12:31 -04:00
arch-v32 cris: don't use module_init for non-modular core intmem.c code 2015-06-16 14:12:30 -04:00
boot CRIS: add Axis 88 board device tree 2015-03-25 09:50:46 +01:00
configs kconfig: rename CONFIG_EMBEDDED to CONFIG_EXPERT 2011-01-20 17:02:05 -08:00
include CRIS changes for 4.1 2015-04-26 13:31:05 -07:00
kernel CRISv32: use GENERIC_SCHED_CLOCK 2015-03-25 11:03:41 +01:00
mm CRIS changes for 3.20 2015-02-15 18:02:02 -08:00
Kconfig CRISv32: use GENERIC_SCHED_CLOCK 2015-03-25 11:03:41 +01:00
Kconfig.debug Kconfig: remove a few puzzling comments 2011-10-31 10:58:48 +01:00
Makefile CRISv32: add device tree support 2015-03-25 09:49:48 +01:00