summaryrefslogtreecommitdiffstats
path: root/block/Kconfig
diff options
context:
space:
mode:
authorMatthew Wilcox <matthew@wil.cx>2006-12-04 03:38:31 -0700
committerLinus Torvalds <torvalds@woody.osdl.org>2006-12-04 19:41:15 -0800
commite62438630ca37539c8cc1553710bbfaa3cf960a7 (patch)
tree83d3e0e016facfee73afba23d306034d60d87495 /block/Kconfig
parent2d941e99dfa2f58f4cf294943274a4f8e264aab7 (diff)
downloadlinux-stable-e62438630ca37539c8cc1553710bbfaa3cf960a7.tar.gz
linux-stable-e62438630ca37539c8cc1553710bbfaa3cf960a7.tar.bz2
linux-stable-e62438630ca37539c8cc1553710bbfaa3cf960a7.zip
[PATCH] Centralise definitions of sector_t and blkcnt_t
CONFIG_LBD and CONFIG_LSF are spread into asm/types.h for no particularly good reason. Centralising the definition in linux/types.h means that arch maintainers don't need to bother adding it, as well as fixing the problem with x86-64 users being asked to make a decision that has absolutely no effect. The H8/300 porters seem particularly confused since I'm not aware of any microcontrollers that need to support 2TB filesystems. Signed-off-by: Matthew Wilcox <matthew@wil.cx> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'block/Kconfig')
-rw-r--r--block/Kconfig6
1 files changed, 2 insertions, 4 deletions
diff --git a/block/Kconfig b/block/Kconfig
index 83766a6bdee2..a50f48111647 100644
--- a/block/Kconfig
+++ b/block/Kconfig
@@ -19,11 +19,9 @@ config BLOCK
if BLOCK
-#XXX - it makes sense to enable this only for 32-bit subarch's, not for x86_64
-#for instance.
config LBD
bool "Support for Large Block Devices"
- depends on X86 || (MIPS && 32BIT) || PPC32 || (S390 && !64BIT) || SUPERH || UML
+ depends on !64BIT
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
@@ -44,7 +42,7 @@ config BLK_DEV_IO_TRACE
config LSF
bool "Support for Large Single Files"
- depends on X86 || (MIPS && 32BIT) || PPC32 || ARCH_S390_31 || SUPERH || UML
+ depends on !64BIT
help
Say Y here if you want to be able to handle very large files (bigger
than 2TB), otherwise say N.