From: aq <aquynh@gmail.com>
To: Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fs/Kconfig: more consistent configuration of XFS
Date: Thu, 28 Apr 2005 18:21:52 +0900 [thread overview]
Message-ID: <9cde8bff05042802213ec650e0@mail.gmail.com> (raw)
In-Reply-To: <20050428083922.GA11542@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
On 4/28/05, Christoph Hellwig <hch@infradead.org> wrote:
> On Thu, Apr 28, 2005 at 05:38:40PM +0900, aq wrote:
> > I dont see why we should keep a file in kernel tree without using it
> > (since the patch removes "source xfs/Kconfig). Anyway, here is another
> > patch that doesnt remove fs/xfs/Kconfig.
>
> No, you should not remove usage of it either.
>
OK, here is another patch. It is up to Andrew to pick the approriate.
But I still prefer the first patch, which provides both consistency in
interface and configuration.
What this patch does:
- Remove "menu" directive from fs/xfs/Kconfig, so XFS configuration is
done in the same screen as other filesystems.
- Move "config XFS_EXPORT " to the bottom, so the menu items aligns
better and consistent with others.
# diffstat makefile.fs3.patch
Kconfig | 11 ++++-------
1 files changed, 4 insertions(+), 7 deletions(-)
Signed-off-by: Nguyen Anh Quynh <aquynh@gmail.com>
[-- Attachment #2: makefile.fs3.patch --]
[-- Type: application/octet-stream, Size: 818 bytes --]
diff -Nurp -X dontdiff-aq a/2.6.12-rc3/fs/xfs/Kconfig c/2.6.12-rc3/fs/xfs/Kconfig
--- a/2.6.12-rc3/fs/xfs/Kconfig 2005-03-02 16:38:08.000000000 +0900
+++ c/2.6.12-rc3/fs/xfs/Kconfig 2005-04-28 17:51:47.000000000 +0900
@@ -1,5 +1,3 @@
-menu "XFS support"
-
config XFS_FS
tristate "XFS filesystem support"
select EXPORTFS if NFSD!=n
@@ -20,10 +18,6 @@ config XFS_FS
system of your root partition is compiled as a module, you'll need
to use an initial ramdisk (initrd) to boot.
-config XFS_EXPORT
- bool
- default y if XFS_FS && EXPORTFS
-
config XFS_RT
bool "Realtime support (EXPERIMENTAL)"
depends on XFS_FS && EXPERIMENTAL
@@ -82,4 +76,7 @@ config XFS_POSIX_ACL
If you don't know what Access Control Lists are, say N.
-endmenu
+config XFS_EXPORT
+ bool
+ default y if XFS_FS && EXPORTFS
+
next prev parent reply other threads:[~2005-04-28 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 7:55 [PATCH] fs/Kconfig: more consistent configuration of XFS aq
2005-04-28 8:05 ` Chris Wedgwood
2005-04-28 8:09 ` Christoph Hellwig
2005-04-28 8:38 ` aq
2005-04-28 8:39 ` Christoph Hellwig
2005-04-28 9:21 ` aq [this message]
2005-04-29 21:28 ` Sam Ravnborg
2005-04-30 2:02 ` aq
2005-04-30 6:09 ` Sam Ravnborg
2005-05-01 11:26 ` aq
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=9cde8bff05042802213ec650e0@mail.gmail.com \
--to=aquynh@gmail.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--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