mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org,
	Linux Filesystem Development <linux-fsdevel@vger.kernel.org>
Subject: [PATCH] config: Fix CONFIG_LFS option
Date: Tue, 28 Mar 2006 17:18:39 -0500	[thread overview]
Message-ID: <1143584319.8199.34.camel@lade.trondhjem.org> (raw)

The help text says that if you select CONFIG_LBD, then it will
automatically select CONFIG_LFS. Nope... That isn't currently the
case.

 - Fix CONFIG_LBD to automatically select CONFIG_LFS
 - Get rid of the cruft in the help text mentioning CONFIG_LBD
 - Tell unsure users to select CONFIG_LFS.

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
---

 block/Kconfig |   11 ++++++-----
 1 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/block/Kconfig b/block/Kconfig
index 5536839..8b4762c 100644
--- a/block/Kconfig
+++ b/block/Kconfig
@@ -6,6 +6,7 @@ #for instance.
 config LBD
 	bool "Support for Large Block Devices"
 	depends on X86 || (MIPS && 32BIT) || PPC32 || (S390 && !64BIT) || SUPERH || UML
+	select LSF
 	help
 	  Say Y here if you want to attach large (bigger than 2TB) discs to
 	  your machine, or if you want to have a raid or loopback device
@@ -27,10 +28,10 @@ config BLK_DEV_IO_TRACE
 config LSF
 	bool "Support for Large Single Files"
 	depends on X86 || (MIPS && 32BIT) || PPC32 || ARCH_S390_31 || SUPERH || UML
-	default n
-	help
-	  When CONFIG_LBD is disabled, say Y here if you want to
-	  handle large file(bigger than 2TB), otherwise say N.
-	  When CONFIG_LBD is enabled, Y is set automatically.
+	help
+	  Say Y here if you want to be able to handle very large files (bigger
+	  than 2TB), otherwise say N.
+
+	  If unsure, say Y.
 
 source block/Kconfig.iosched

             reply	other threads:[~2006-03-28 22:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 22:18 Trond Myklebust [this message]
2006-03-28 22:34 ` Linus Torvalds
2006-03-28 22:44   ` Andrew Morton
2006-03-28 22:48   ` Trond Myklebust

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=1143584319.8199.34.camel@lade.trondhjem.org \
    --to=trond.myklebust@netapp.com \
    --cc=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®