From: Stephen Hemminger <shemminger@osdl.org>
To: Tom Zanussi <zanussi@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, karim@opersys.com, bob@watson.ibm.com
Subject: [PATCH] relayfs
Date: Wed, 16 Jul 2003 14:55:08 -0700 [thread overview]
Message-ID: <20030716145508.1742d722.shemminger@osdl.org> (raw)
In-Reply-To: <16148.6807.578262.720332@gargle.gargle.HOWL>
Shouldn't relayfs be in the "Pseudo filesystems" part of Kconfig.
Also don't need the .ko suffix.
diff -Nru a/fs/Kconfig b/fs/Kconfig
--- a/fs/Kconfig Wed Jul 16 14:49:58 2003
+++ b/fs/Kconfig Wed Jul 16 14:49:58 2003
@@ -881,6 +881,26 @@
say M here and read <file:Documentation/modules.txt>. The module
will be called ramfs.
+config RELAYFS_FS
+ tristate "Relayfs file system support"
+ ---help---
+ Relayfs is a high-speed data relay filesystem designed to provide
+ an efficient mechanism for tools and facilities to relay large
+ amounts of data from kernel space to user space. It's not useful
+ on its own, and should only be enabled if other facilities that
+ need it are enabled, such as for example dynamic printk or the
+ Linux Trace Toolkit.
+
+ See <file:Documentation/filesystems/relayfs.txt> for further
+ information.
+
+ This file system is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module is called relayfs. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
+
+ If unsure, say N.
+
endmenu
menu "Miscellaneous filesystems"
@@ -1220,26 +1240,6 @@
will be called sysv.
If you haven't heard about all of this before, it's safe to say N.
-
-config RELAYFS_FS
- tristate "Relayfs file system support"
- ---help---
- Relayfs is a high-speed data relay filesystem designed to provide
- an efficient mechanism for tools and facilities to relay large
- amounts of data from kernel space to user space. It's not useful
- on its own, and should only be enabled if other facilities that
- need it are enabled, such as for example dynamic printk or the
- Linux Trace Toolkit.
-
- See <file:Documentation/filesystems/relayfs.txt> for further
- information.
-
- This file system is also available as a module ( = code which can be
- inserted in and removed from the running kernel whenever you want).
- The module is called relayfs.ko. If you want to compile it as a
- module, say M here and read <file:Documentation/modules.txt>.
-
- If unsure, say N.
config UFS_FS
tristate "UFS file system support (read only)"
next prev parent reply other threads:[~2003-07-16 21:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 15:15 [RFC][PATCH 0/5] relayfs Tom Zanussi
2003-07-15 15:27 ` Gianni Tedesco
2003-07-15 16:01 ` Tom Zanussi
2003-07-15 16:40 ` Gianni Tedesco
2003-07-15 17:01 ` Tom Zanussi
2003-07-15 18:45 ` Tom Zanussi
2003-07-16 21:55 ` Stephen Hemminger [this message]
2003-07-16 22:27 ` [PATCH] relay_open const filename Stephen Hemminger
2003-07-18 21:11 ` [PATCH] relayfs Tom Zanussi
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=20030716145508.1742d722.shemminger@osdl.org \
--to=shemminger@osdl.org \
--cc=bob@watson.ibm.com \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zanussi@us.ibm.com \
/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
all inboxes | Powered by JetHome®