From: Adrian Bunk <bunk@stusta.de>
To: ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [Ocfs2-devel] [-mm patch] CONFIGFS_FS: "If unsure, say N."
Date: Thu, 30 Jun 2005 03:10:15 +0200 [thread overview]
Message-ID: <20050630011015.GC27478@stusta.de> (raw)
In-Reply-To: <20050630005723.GE23823@ca-server1.us.oracle.com>
On Wed, Jun 29, 2005 at 05:57:23PM -0700, Joel Becker wrote:
> On Thu, Jun 30, 2005 at 02:47:38AM +0200, Adrian Bunk wrote:
> > But I get your point, what about the patch below?
>
> Non-descriptive. We are descriptive for sysfs (and even allow
> the choice!). I'd say that leaving the description but perhaps adding
> the caveat about modules and unsure-N might be a good way to go.
The question is:
Assume a user doesn't use external modules, will enabling this option
have any effect for him except that it wastes some bytes of his RAM?
sysfs is useful in this case.
How is configfs useful in this case?
> Joel
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-06-30 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 8:03 [-mm patch] CONFIGFS_FS shouldn't be user-visible Adrian Bunk
2005-06-29 21:30 ` Joel Becker
2005-06-30 0:47 ` [-mm patch] CONFIGFS_FS: "If unsure, say N." Adrian Bunk
2005-06-30 0:57 ` [Ocfs2-devel] " Joel Becker
2005-06-30 1:10 ` Adrian Bunk [this message]
2005-06-30 1:30 ` Joel Becker
2005-07-02 10:58 ` Adrian Bunk
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=20050630011015.GC27478@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.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