Messages in this thread Patch in this message | | | Date | Thu, 11 Jun 2009 04:46:30 +0200 | From | Tomáš Szépe <> | Subject | [2.6.29.x+ FIX] CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK |
| |
Hello,
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@pinerecords.com>
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 @@ bool default n +source "fs/xfs/Kconfig" +source "fs/gfs2/Kconfig" +source "fs/ocfs2/Kconfig" +source "fs/btrfs/Kconfig" + +endif # BLOCK + config FILE_LOCKING 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |