All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tomáš Szépe" <szepe@pinerecords.com>
To: gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: [2.6.28.x FIX] CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK
Date: Thu, 11 Jun 2009 04:40:19 +0200	[thread overview]
Message-ID: <20090611024019.GC25384@louise.pinerecords.com> (raw)

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@pinerecords.com>

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

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11  2:40 Tomáš Szépe [this message]
2009-06-11  2:46 ` [2.6.28.x FIX] CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK Greg KH
2009-06-11  3:07   ` Tomáš Szépe
2009-06-11  3:49     ` Greg KH

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=20090611024019.GC25384@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.