From: Daniel Baluta <daniel.baluta@intel.com>
To: viro@zeniv.linux.org.uk, hch@lst.de, jlbec@evilplan.org
Cc: linux-fsdevel@vger.kernel.org, lars@metafoo.de,
daniel.baluta@intel.com, linux-kernel@vger.kernel.org
Subject: [RESEND PATCH] configfs: init configfs module earlier at boot time
Date: Tue, 7 Apr 2015 18:56:11 +0300 [thread overview]
Message-ID: <1428422171-3180-1-git-send-email-daniel.baluta@intel.com> (raw)
We need this earlier in the boot process to allow various subsystems
to use configfs (e.g Industrial IIO).
Also, debugfs is at core_initcall level and configfs should be on
the same level from infrastructure point of view.
Suggested-by: Lars-Peter Clausen <lars@metafoo.de>
Signed-off-by: Daniel Baluta <daniel.baluta@intel.com>
---
* Extended CC list with Al, Christoph and fsdevel :)
fs/configfs/mount.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/configfs/mount.c b/fs/configfs/mount.c
index da94e41..5373567 100644
--- a/fs/configfs/mount.c
+++ b/fs/configfs/mount.c
@@ -173,5 +173,5 @@ MODULE_LICENSE("GPL");
MODULE_VERSION("0.0.2");
MODULE_DESCRIPTION("Simple RAM filesystem for user driven kernel subsystem configuration.");
-module_init(configfs_init);
+core_initcall(configfs_init);
module_exit(configfs_exit);
--
1.9.1
next reply other threads:[~2015-04-07 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 15:56 Daniel Baluta [this message]
2015-04-13 9:44 ` [RESEND PATCH] configfs: init configfs module earlier at boot time Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2015-04-24 9:46 Daniel Baluta
2015-03-18 19:56 Daniel Baluta
2015-04-02 7:34 ` Daniel Baluta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1428422171-3180-1-git-send-email-daniel.baluta@intel.com \
--to=daniel.baluta@intel.com \
--cc=hch@lst.de \
--cc=jlbec@evilplan.org \
--cc=lars@metafoo.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.