linux/fs/ramfs
Paul Gortmaker af52b040eb fs/ramfs: don't use module_init for non-modular core code
The ramfs is always built in.  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.

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 fs_initcall (which makes sense for fs code)
will thus change this registration from level 6-device to level 5-fs
(i.e. slightly earlier).  However no observable impact of that small
difference has been observed during testing, or is expected.

Also note that this change uncovers a missing semicolon bug in the
registration of the initcall.

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2014-01-21 16:19:42 -08:00
..
Makefile Remove valueless definition of hard-selected RAMFS option 2007-10-17 08:42:56 -07:00
file-mmu.c fs: convert simple fs to new truncate 2010-05-27 22:15:47 -04:00
file-nommu.c new helper: file_inode(file) 2013-02-22 23:31:31 -05:00
inode.c fs/ramfs: don't use module_init for non-modular core code 2014-01-21 16:19:42 -08:00
internal.h fs/ramfs/ extern cleanup 2008-04-29 08:06:00 -07:00