• Paul Gortmaker's avatar
    m68k/mvme16x: rtc - Don't use module_init in non-modular code · 51ad77ad
    Paul Gortmaker authored
    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: default avatarPaul Gortmaker <paul.gortmaker@windriver.com>
    Signed-off-by: default avatarGeert Uytterhoeven <geert@linux-m68k.org>
    51ad77ad
rtc.c 3.71 KB