diff options
author | Paul Gortmaker <paul.gortmaker@windriver.com> | 2015-05-02 02:08:20 +0200 |
---|---|---|
committer | Paul Gortmaker <paul.gortmaker@windriver.com> | 2015-06-16 20:12:34 +0200 |
commit | a4bc6fc79f94c5b4f850aabca9c5249adc597094 (patch) | |
tree | 1faadefb5f87e54a834db6f64a15c91c55bf7b14 /samples | |
parent | Linux 4.1-rc8 (diff) | |
download | linux-a4bc6fc79f94c5b4f850aabca9c5249adc597094.tar.xz linux-a4bc6fc79f94c5b4f850aabca9c5249adc597094.zip |
mm: replace module_init usages with subsys_initcall in nommu.c
Compiling some arm/m68k configs with "# CONFIG_MMU is not set" reveals
two more instances of module_init being used for code that can't
possibly be modular, as CONFIG_MMU is either on or off.
We replace them with subsys_initcall as per what was done in other
mmu-enabled code.
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 subsys_initcall (which makes sense for these
files) will thus change this registration from level 6-device to level
4-subsys (i.e. slightly earlier).
One might think that core_initcall (l2) or postcore_initcall (l3) would
be more appropriate for anything in mm/ but if we look at the actual init
functions themselves, we see they are just sysctl setup stuff, and
hence the choice of subsys_initcall (l4) seems reasonable. At the same
time it minimizes the risk of changing the priority too drastically all
at once. We can adjust further in the future.
Also, a couple instances of missing ";" at EOL are fixed.
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions