[2.6.28.x FIX] CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK

[TomÃÅ SzÃpe]

Hello,

Fix: CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK.
Patch against 2.6.28.10.

inlined please find a trivial fix that makes it possible to run
complete systems out of an initramfs on 2.6.28.10 again (this
broke somewhere between 2.6.27 and 2.6.28).

-- 
TomÃÅ SzÃpe <szepe@xxxxxxxxxxxxxxx>

diff -urN a/fs/Kconfig b/fs/Kconfig
--- a/fs/Kconfig	2008-12-25 00:26:37 +0100
+++ b/fs/Kconfig	2009-06-11 04:23:12 +0200
@@ -172,14 +172,6 @@
 	bool
 	default n
 
-config FILE_LOCKING
-	bool "Enable POSIX file locking API" if EMBEDDED
-	default y
-	help
-	  This option enables standard file locking support, required
-          for filesystems like NFS and for the flock() system
-          call. Disabling this option saves about 11k.
-
 source "fs/xfs/Kconfig"
 source "fs/gfs2/Kconfig"
 
@@ -270,6 +262,14 @@
 
 endif # BLOCK
 
+config FILE_LOCKING
+	bool "Enable POSIX file locking API" if EMBEDDED
+	default y
+	help
+	  This option enables standard file locking support, required
+          for filesystems like NFS and for the flock() system
+          call. Disabling this option saves about 11k.
+
 config DNOTIFY
 	bool "Dnotify support"
 	default y
--
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/