public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tomáš Szépe" <szepe@pinerecords.com>
To: gregkh@suse.de, akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [2.6.29.x+ FIX] CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK
Date: Thu, 11 Jun 2009 04:46:30 +0200	[thread overview]
Message-ID: <20090611024630.GA24852@louise.pinerecords.com> (raw)

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"

             reply	other threads:[~2009-06-11  2:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11  2:46 Tomáš Szépe [this message]
2009-06-15 21:45 ` [2.6.29.x+ FIX] CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK Andrew Morton
2009-06-15 21:57   ` Tomáš Szépe

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=20090611024630.GA24852@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.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