Remove valueless definition of hard-selected RAMFS option

Since CONFIG_RAMFS is currently hard-selected to "y", and since
Documentation/filesystems/ramfs-rootfs-initramfs.txt reads as follows:

"The amount of code required to implement ramfs is tiny, because all the
work is done by the existing Linux caching infrastructure.  Basically,
you're mounting the disk cache as a filesystem.  Because of this, ramfs is
not an optional component removable via menuconfig, since there would be
negligible space savings."

It seems pointless to leave this as a Kconfig entry.

Signed-off-by: Robert P. J. Day <rpjday@mindspring.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

1 files changed, 0 insertions, 14 deletions

diff --git a/fs/Kconfig b/fs/Kconfig
index 9a40a9c665c7..f0df9a2e19e1 100644
--- a/fs/Kconfig
+++ b/fs/Kconfig
@@ -999,20 +999,6 @@ config HUGETLBFS
 config HUGETLB_PAGE
         def_bool HUGETLBFS
 
-config RAMFS
-        bool
-        default y
-        ---help---
-          Ramfs is a file system which keeps all files in RAM. It allows
-          read and write access.
-
-          It is more of an programming example than a useable file system.  If
-          you need a file system which lives in RAM with limit checking use
-          tmpfs.
-
-          To compile this as a module, choose M here: the module will be called
-          ramfs.
-
 config CONFIGFS_FS
         tristate "Userspace-driven configuration filesystem (EXPERIMENTAL)"
         depends on SYSFS && EXPERIMENTAL