[2.6.29.x+ FIX] CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK

From: TomÃÅ SzÃpe
Date: Wed Jun 10 2009 - 22:46:46 EST


Fix: CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK.
Patch against 2.6.29.*, 2.6.30, current.

inlined please find a trivial fix that makes it possible to run
complete systems out of an initramfs on current kernels again
(this last worked on 2.6.27.*).

TomÃÅ SzÃpe <szepe@xxxxxxxxxxxxxxx>

diff -urN a/fs/Kconfig b/fs/Kconfig
--- a/fs/Kconfig 2009-06-10 05:05:27 +0200
+++ b/fs/Kconfig 2009-06-11 03:50:50 +0200
@@ -39,6 +39,13 @@
default n

+source "fs/xfs/Kconfig"
+source "fs/gfs2/Kconfig"
+source "fs/ocfs2/Kconfig"
+source "fs/btrfs/Kconfig"
+endif # BLOCK
bool "Enable POSIX file locking API" if EMBEDDED
default y
@@ -47,13 +54,6 @@
for filesystems like NFS and for the flock() system
call. Disabling this option saves about 11k.

-source "fs/xfs/Kconfig"
-source "fs/gfs2/Kconfig"
-source "fs/ocfs2/Kconfig"
-source "fs/btrfs/Kconfig"
-endif # BLOCK
source "fs/notify/Kconfig"

source "fs/quota/Kconfig"
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/