public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: xfs-masters@oss.sgi.com
Cc: nathans@sgi.com, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: [PATCH] pull XFS support out of Kconfig submenu
Date: Wed, 17 Aug 2005 22:45:48 +0200	[thread overview]
Message-ID: <200508172245.49043.jesper.juhl@gmail.com> (raw)

It seems slightly odd to me that XFS support should be in a separate submenu,
when all the other filesystems are not using submenus but are directly 
selectable from the Filesystems menu.
This patch makes XFS Kconfig entries behave like everything else.

Ignore if there's a good reason for the menu, please consider applying 
otherwise.

Please Cc: me on replies.


Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
---

 fs/xfs/Kconfig |    5 +----
 1 files changed, 1 insertion(+), 4 deletions(-)

--- linux-2.6.13-rc6-git9-orig/fs/xfs/Kconfig	2005-06-17 21:48:29.000000000 +0200
+++ linux-2.6.13-rc6-git9/fs/xfs/Kconfig	2005-08-17 22:38:26.000000000 +0200
@@ -1,5 +1,3 @@
-menu "XFS support"
-
 config XFS_FS
 	tristate "XFS filesystem support"
 	select EXPORTFS if NFSD!=n
@@ -22,6 +20,7 @@
 
 config XFS_EXPORT
 	bool
+	depends on XFS_FS
 	default y if XFS_FS && EXPORTFS
 
 config XFS_RT
@@ -81,5 +80,3 @@
 	  Linux website <http://acl.bestbits.at/>.
 
 	  If you don't know what Access Control Lists are, say N.
-
-endmenu



             reply	other threads:[~2005-08-17 20:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-17 20:45 Jesper Juhl [this message]
2005-08-18 13:53 ` [PATCH] pull XFS support out of Kconfig submenu Chris Wedgwood
2005-08-18 15:22   ` [xfs-masters] " Russell Cattelan
2005-08-18 22:55     ` Nathan Scott
2005-08-18 15:23   ` Eric Sandeen
2005-08-18 15:32     ` Eric Sandeen
  -- strict thread matches above, loose matches on Subject: below --
2005-08-17 20:44 Jesper Juhl

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=200508172245.49043.jesper.juhl@gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=nathans@sgi.com \
    --cc=xfs-masters@oss.sgi.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