From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: RFC: kill msdos and vfat modules?
Date: Thu, 04 Jun 2009 10:26:22 +0900 [thread overview]
Message-ID: <871vq0lrgh.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20090603143200.GA5778@lst.de> (Christoph Hellwig's message of "Wed, 3 Jun 2009 16:32:00 +0200")
Christoph Hellwig <hch@lst.de> writes:
> There's almost no code left in the msdos and vfat modules with all
> the guts in the shared fat module. Shouldn't we just do away with
> the vfat and msdos modules and just provide module aliases in the
> main fat module?
I have no objection to it if it works. Maybe, one concern is the order
of detection (rootfs, /proc/filesystems) when it's not moudle. (however,
probably it's not hard to control).
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2009-06-04 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 14:32 RFC: kill msdos and vfat modules? Christoph Hellwig
2009-06-04 1:26 ` OGAWA Hirofumi [this message]
2009-06-08 7:32 ` Christoph Hellwig
2009-06-08 12:20 ` OGAWA Hirofumi
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=871vq0lrgh.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=hch@lst.de \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).