From: Adrian Bunk <bunk@stusta.de>
To: Manish Singh <manish.singh@oracle.com>
Cc: Mark Fasheh <mark.fasheh@oracle.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org, torvalds@osdl.org,
linux-fsdevel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] Re: [RFC] [PATCH] OCFS2
Date: Thu, 19 May 2005 11:45:17 +0200 [thread overview]
Message-ID: <20050519094517.GD5112@stusta.de> (raw)
In-Reply-To: <20050519012658.GA27595@ca-server1.us.oracle.com>
On Wed, May 18, 2005 at 06:26:58PM -0700, Manish Singh wrote:
> On Thu, May 19, 2005 at 01:40:22AM +0200, Adrian Bunk wrote:
> > On Wed, May 18, 2005 at 03:33:03PM -0700, Mark Fasheh wrote:
> > >...
> > > A full patch can be downloaded from:
> > > http://oss.oracle.com/projects/ocfs2/dist/files/patches/2.6.12-rc4/complete/ocfs2-configfs-all.patch
> > >...
> >
> > Some comments on this patch:
> > - there's no reason to make JBD user-visible
>
> Sure, the only reason I made it visible was because of the comment in
> there:
>
> # CONFIG_JBD could be its own option (even modular), but until there are
> # other users than ext3, we will simply make it be the same as CONFIG_EXT3_FS
>
> I don't really have a preference either way.
I'd say the comment is wrong.
> > - is there any reason why CONFIGFS_FS is user-visible?
>
> It's a generic mechanism for userspace driven configuration of kernel
> functionality. There's nothing specific to OCFS2 about it. Other kernel
> subsystems/projects could use it too, for their own configuration
> mechanisms. More details are in configfs.txt, which is included in the
> above patch. Note the example used in the documentation text is an NBD
> driver.
>...
If other subsystems use it, they should select it.
> -Manish
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-05-19 9:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 22:33 [RFC] [PATCH] OCFS2 Mark Fasheh
2005-05-18 23:35 ` Hans Reiser
2005-05-18 23:40 ` Adrian Bunk
2005-05-19 1:26 ` [Ocfs2-devel] " Manish Singh
2005-05-19 9:45 ` Adrian Bunk [this message]
2005-05-19 2:30 ` Kyle Moffett
2005-05-19 4:30 ` Mark Fasheh
2005-05-19 6:30 ` Daniel Phillips
2005-05-19 6:54 ` Mark Fasheh
2005-05-19 16:23 ` Daniel Phillips
2005-05-19 10:26 ` Jeff Garzik
2005-05-19 15:20 ` Lee Revell
2005-05-19 15:25 ` Jeff Garzik
2005-06-23 18:03 ` James Morris
2005-06-23 18:29 ` Mark Fasheh
2005-06-24 3:05 ` Paul Jackson
2005-06-24 3:29 ` Paul Jackson
2005-06-24 3:59 ` Mark Fasheh
2005-06-24 4:17 ` Paul Jackson
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=20050519094517.GD5112@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manish.singh@oracle.com \
--cc=mark.fasheh@oracle.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).