linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: linux-fsdevel@vger.kernel.org
Cc: swhiteho@redhat.com, akpm <akpm@osdl.org>
Subject: [PATCH] DLM needs SYSFS
Date: Fri, 17 Nov 2006 23:30:13 -0800	[thread overview]
Message-ID: <20061117233013.e8b8797d.randy.dunlap@oracle.com> (raw)

From: Randy Dunlap <randy.dunlap@oracle.com>

DLM uses/needs SYSFS (kernel_subsys).
This also prevents DLM from being able to select CONFIGFS,
which also uses SYSFS and caused yet another build error.

Also fix Kconfig help text formatting to use kernel indentation
convention.

(It seems odd that the menu for DLM depends on
INET && IP_SCTP && EXPERIMENTAL, but DLM depends on
a different list of symbols.)

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 fs/dlm/Kconfig |   12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

--- linux-2619-rc6.orig/fs/dlm/Kconfig
+++ linux-2619-rc6/fs/dlm/Kconfig
@@ -3,18 +3,18 @@ menu "Distributed Lock Manager"
 
 config DLM
 	tristate "Distributed Lock Manager (DLM)"
-	depends on IPV6 || IPV6=n
+	depends on (IPV6 || IPV6=n) && SYSFS
 	select CONFIGFS_FS
 	help
-	A general purpose distributed lock manager for kernel or userspace
-	applications.
+	  A general purpose distributed lock manager for kernel or userspace
+	  applications.
 
 config DLM_DEBUG
 	bool "DLM debugging"
 	depends on DLM
 	help
-	Under the debugfs mount point, the name of each lockspace will
-	appear as a file in the "dlm" directory.  The output is the
-	list of resource and locks the local node knows about.
+	  Under the debugfs mount point, the name of each lockspace will
+	  appear as a file in the "dlm" directory.  The output is the
+	  list of resource and locks the local node knows about.
 
 endmenu


---

                 reply	other threads:[~2006-11-18  7:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20061117233013.e8b8797d.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=swhiteho@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).