linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sage Weil <sage@newdream.net>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	greg@kroah.com
Cc: Sage Weil <sage@newdream.net>
Subject: [PATCH 01/21] fs: add fs/staging directory
Date: Fri, 19 Jun 2009 15:31:22 -0700	[thread overview]
Message-ID: <1245450702-31343-2-git-send-email-sage@newdream.net> (raw)
In-Reply-To: <1245450702-31343-1-git-send-email-sage@newdream.net>

Add an fs/staging directory, analogous to drivers/staging, for file
systems that are not yet ready to be merged into the kernel proper.
This makes them easier to find by keeping them under the appropriate
menu/section.  It also makes them accessible when ARCH=um, which hides
the entire drivers tree.

As with drivers/staging, modules from fs/staging are marked with 'staging'
by modpost.

Evgeniy's pohmelfs (drivers/staging/pohmelfs) should presumably be moved
to fs/staging/pohmelfs.

Signed-off-by: Sage Weil <sage@newdream.net>
---
 fs/Kconfig             |    2 ++
 fs/Makefile            |    1 +
 fs/staging/Kconfig     |   46 ++++++++++++++++++++++++++++++++++++++++++++++
 fs/staging/Makefile    |    5 +++++
 fs/staging/fsstaging.c |   19 +++++++++++++++++++
 scripts/mod/modpost.c  |    4 +++-
 6 files changed, 76 insertions(+), 1 deletions(-)
 create mode 100644 fs/staging/Kconfig
 create mode 100644 fs/staging/Makefile
 create mode 100644 fs/staging/fsstaging.c

diff --git a/fs/Kconfig b/fs/Kconfig
index 9f7270f..3374de2 100644
--- a/fs/Kconfig
+++ b/fs/Kconfig
@@ -265,4 +265,6 @@ endif
 source "fs/nls/Kconfig"
 source "fs/dlm/Kconfig"
 
+source "fs/staging/Kconfig"
+
 endmenu
diff --git a/fs/Makefile b/fs/Makefile
index af6d047..a6e3c51 100644
--- a/fs/Makefile
+++ b/fs/Makefile
@@ -64,6 +64,7 @@ obj-$(CONFIG_DLM)		+= dlm/
  
 # Do not add any filesystems before this line
 obj-$(CONFIG_FSCACHE)		+= fscache/
+obj-$(CONFIG_FSSTAGING)		+= staging/
 obj-$(CONFIG_REISERFS_FS)	+= reiserfs/
 obj-$(CONFIG_EXT3_FS)		+= ext3/ # Before ext2 so root fs can be ext3
 obj-$(CONFIG_EXT2_FS)		+= ext2/
diff --git a/fs/staging/Kconfig b/fs/staging/Kconfig
new file mode 100644
index 0000000..605d8ae
--- /dev/null
+++ b/fs/staging/Kconfig
@@ -0,0 +1,46 @@
+menuconfig FSSTAGING
+	bool "Staging file systems"
+	default n
+	---help---
+	  This option allows you to select a number of file systems
+	  that are not of the "normal" Linux kernel quality level.
+	  These are placed here in order to get a wider audience to
+	  make use of them.  Please note that these are under heavy
+	  development, may or may not work, and may contain userspace
+	  interfaces that most likely will be changed in the near
+	  future.
+
+	  Using any of these file systems will taint your kernel which
+	  might affect support options from both the community, and
+	  various commercial support organizations.
+
+	  If you wish to work on these file systems, to help improve
+	  them, or to report problems you have with them, please see
+	  the fs_name.README file in the fs/staging/ directory to see
+	  what needs to be worked on, and who to contact.
+
+	  If in doubt, say N here.
+
+
+if FSSTAGING
+
+config FSSTAGING_EXCLUDE_BUILD
+	bool "Exclude Staging file systems from being built" if FSSTAGING
+	default y
+	---help---
+	  Are you sure you really want to build the staging file
+	  systems?  They taint your kernel, don't live up to the
+	  normal Linux kernel quality standards, are a bit crufty
+	  around the edges, and might go off and kick your dog when
+	  you aren't paying attention.
+
+	  Say N here to be able to select and build the Staging file
+	  systems.  This option is primarily here to prevent them from
+	  being built when selecting 'make allyesconfg' and 'make
+	  allmodconfig' so don't be all that put off, your dog will be
+	  just fine.
+
+if !FSSTAGING_EXCLUDE_BUILD
+
+endif # !FSSTAGING_EXCLUDE_BUILD
+endif # FSSTAGING
diff --git a/fs/staging/Makefile b/fs/staging/Makefile
new file mode 100644
index 0000000..7ddeb16
--- /dev/null
+++ b/fs/staging/Makefile
@@ -0,0 +1,5 @@
+# Makefile for fs/staging directory
+
+# fix for build system bug...
+obj-$(CONFIG_FSSTAGING)		+= fsstaging.o
+
diff --git a/fs/staging/fsstaging.c b/fs/staging/fsstaging.c
new file mode 100644
index 0000000..c9a0a8c
--- /dev/null
+++ b/fs/staging/fsstaging.c
@@ -0,0 +1,19 @@
+#include <linux/kernel.h>
+#include <linux/init.h>
+#include <linux/module.h>
+
+static int __init fsstaging_init(void)
+{
+	return 0;
+}
+
+static void __exit fsstaging_exit(void)
+{
+}
+
+module_init(fsstaging_init);
+module_exit(fsstaging_exit);
+
+MODULE_AUTHOR("Sage Weil <sage@newdream.net>");
+MODULE_DESCRIPTION("FS Staging Core");
+MODULE_LICENSE("GPL");
diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
index 161b784..3e92bbe 100644
--- a/scripts/mod/modpost.c
+++ b/scripts/mod/modpost.c
@@ -1721,8 +1721,10 @@ static void add_header(struct buffer *b, struct module *mod)
 void add_staging_flag(struct buffer *b, const char *name)
 {
 	static const char *staging_dir = "drivers/staging";
+	static const char *fsstaging_dir = "fs/staging";
 
-	if (strncmp(staging_dir, name, strlen(staging_dir)) == 0)
+	if (strncmp(staging_dir, name, strlen(staging_dir)) == 0 ||
+	    strncmp(fsstaging_dir, name, strlen(fsstaging_dir)) == 0)
 		buf_printf(b, "\nMODULE_INFO(staging, \"Y\");\n");
 }
 
-- 
1.5.6.5


  reply	other threads:[~2009-06-19 22:30 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19 22:31 [PATCH 00/21] ceph: Ceph distributed file system client v0.9 Sage Weil
2009-06-19 22:31 ` Sage Weil [this message]
2009-06-19 22:31   ` [PATCH 02/21] ceph: documentation Sage Weil
2009-06-19 22:31     ` [PATCH 03/21] ceph: on-wire types Sage Weil
2009-06-19 22:31       ` [PATCH 04/21] ceph: client types Sage Weil
2009-06-19 22:31         ` [PATCH 05/21] ceph: super.c Sage Weil
2009-06-19 22:31           ` [PATCH 06/21] ceph: inode operations Sage Weil
2009-06-19 22:31             ` [PATCH 07/21] ceph: directory operations Sage Weil
2009-06-19 22:31               ` [PATCH 08/21] ceph: file operations Sage Weil
2009-06-19 22:31                 ` [PATCH 09/21] ceph: address space operations Sage Weil
2009-06-19 22:31                   ` [PATCH 10/21] ceph: MDS client Sage Weil
2009-06-19 22:31                     ` [PATCH 11/21] ceph: OSD client Sage Weil
2009-06-19 22:31                       ` [PATCH 12/21] ceph: CRUSH mapping algorithm Sage Weil
2009-06-19 22:31                         ` [PATCH 13/21] ceph: monitor client Sage Weil
2009-06-19 22:31                           ` [PATCH 14/21] ceph: capability management Sage Weil
2009-06-19 22:31                             ` [PATCH 15/21] ceph: snapshot management Sage Weil
2009-06-19 22:31                               ` [PATCH 16/21] ceph: messenger library Sage Weil
2009-06-19 22:31                                 ` [PATCH 17/21] ceph: nfs re-export support Sage Weil
2009-06-19 22:31                                   ` [PATCH 18/21] ceph: ioctls Sage Weil
2009-06-19 22:31                                     ` [PATCH 19/21] ceph: debugging Sage Weil
2009-06-19 22:31                                       ` [PATCH 20/21] ceph: debugfs Sage Weil
2009-06-19 22:31                                         ` [PATCH 21/21] ceph: Kconfig, Makefile Sage Weil
2009-06-20  9:12                                   ` [PATCH 17/21] ceph: nfs re-export support Stefan Richter
2009-06-20 20:39                                     ` Sage Weil
2009-06-20 21:22                                       ` Stefan Richter
2009-06-19 22:44 ` [PATCH 00/21] ceph: Ceph distributed file system client v0.9 Greg KH
2009-06-19 23:15   ` Sage Weil
2009-06-19 23:20     ` Greg KH
2009-06-19 22:45 ` Greg KH
2009-06-19 22:54   ` Stephen Rothwell
2009-06-19 23:12   ` Sage Weil
2009-06-19 23:19     ` Greg KH

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=1245450702-31343-2-git-send-email-sage@newdream.net \
    --to=sage@newdream.net \
    --cc=greg@kroah.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).