From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Will Dyson <will_dyson@pobox.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [CFT] [1/15] table-driven filesystems option parsing
Date: Fri, 19 Sep 2003 13:36:48 -0700 [thread overview]
Message-ID: <20030919133648.400ad18e.rddunlap@osdl.org> (raw)
In-Reply-To: <1063826464.17972.897.camel@thalience>
On Wed, 17 Sep 2003 15:21:05 -0400 Will Dyson <will_dyson@pobox.com> wrote:
| On Fri, 2003-09-05 at 14:56, Randy.Dunlap wrote:
|
| > Current (full) patch is at
| > http://developer.osdl.org/rddunlap/patches/linux-260t4g-fsoptions.patch
| >
| > These patches apply to 2.6.0-test4 or -current (Sept. 5/2003).
| >
| > I have tested ext3, ext3, fat, isofs, jfs, & proc.
| >
| > I'd appreciate others testing all of these, please, especially
| > the ones that I can't test (adfs, affs, hfs, hpfs, ufd, ufs,
| > autofs[4]).
|
| As a filesystem maintainer, I like the idea of this patch! However, I
| think it could use some comments on useage in the header file. There are
| already too many filesystem interfaces where the only documentation on
| how to use them is the way that existing filesystems use them.
|
| Below is a patch to convert befs to use parser.h. It kills some of my
| least favorite code (yay!).
|
| The patch is tested a certain minimal amount (booted, mounted a
| filesystem with options).
Thanks for the patch and comments. I'll try to add some usage docs
to it also.
--
~Randy
prev parent reply other threads:[~2003-09-19 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 18:56 Randy.Dunlap
2003-09-17 19:21 ` Will Dyson
2003-09-19 20:36 ` Randy.Dunlap [this message]
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=20030919133648.400ad18e.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will_dyson@pobox.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
all inboxes | Powered by JetHome®