linux/fs/notify/inotify
Paul Gortmaker c013d5a458 fs/notify: don't use module_init for non-modular inotify_user code
The INOTIFY_USER option is bool, and hence this code is either
present 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.

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.

Cc: John McCutchan <john@johnmccutchan.com>
Cc: Robert Love <rlove@rlove.org>
Cc: Eric Paris <eparis@parisplace.org>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
2015-06-16 14:12:34 -04:00
..
inotify_fsnotify.c fsnotify: unify inode and mount marks handling 2014-12-13 12:42:53 -08:00
inotify_user.c fs/notify: don't use module_init for non-modular inotify_user code 2015-06-16 14:12:34 -04:00
inotify.h inotify: Fix reporting of cookies for inotify events 2014-02-18 11:17:17 +01:00
Kconfig inotify: remove inotify in kernel interface 2010-07-28 09:58:31 -04:00
Makefile inotify: remove inotify in kernel interface 2010-07-28 09:58:31 -04:00