From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <alexander.levin@microsoft.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/staging/exfat - by default, prohibit mount of fat/vfat
Date: Sat, 31 Aug 2019 23:37:27 -0400 [thread overview]
Message-ID: <339527.1567309047@turing-police> (raw)
In-Reply-To: <20190901010721.GG7777@dread.disaster.area>
[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]
On Sun, 01 Sep 2019 11:07:21 +1000, Dave Chinner said:
> Totally irrelevant to the issue at hand. You can easily co-ordinate
> out of tree contributions through a github tree, or a tree on
> kernel.org, etc.
Well.. I'm not personally wedded to the staging tree. I'm just interested in
getting a driver done and upstreamed with as little pain as possible. :)
Is there any preference for github versus kernel.org? I can set up a github
tree on my own, no idea who needs to do what for a kernel.org tree.
Also, this (from another email of yours) was (at least to me) the most useful
thing said so far:
> look at what other people have raised w.r.t. to that filesystem -
> on-disk format validation, re-implementation of largely generic
> code, lack of namespacing of functions leading to conflicts with
> generic/VFS functionality, etc.
All of which are now on the to-do list, thanks.
Now one big question:
Should I heave all the vfat stuff overboard and make a module that
*only* does exfat, or is there enough interest in an extended FAT module
that does vfat and extfat, in which case the direction should be to re-align
this module's code with vfat?
> That's the choice you have to make now: listen to the reviewers
> saying "resolve the fundamental issues before goign any further",
Well... *getting* a laundry list of what the reviewers see as the fundamental
issues is the first step in resolving them ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-09-01 3:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 16:42 [PATCH] drivers/staging/exfat - by default, prohibit mount of fat/vfat Valdis Klētnieks
2019-08-30 16:45 ` Christoph Hellwig
2019-08-31 0:48 ` Valdis Klētnieks
2019-08-31 6:46 ` Christoph Hellwig
2019-08-31 10:25 ` Valdis Klētnieks
2019-08-31 14:24 ` Andy Shevchenko
2019-08-31 14:51 ` Valdis Klētnieks
2019-09-01 1:07 ` Dave Chinner
2019-09-01 1:37 ` Gao Xiang
2019-09-01 3:05 ` Al Viro
2019-09-01 3:26 ` Gao Xiang
2019-09-01 3:37 ` Valdis Klētnieks [this message]
2019-09-01 22:43 ` Dave Chinner
2019-09-01 23:13 ` Valdis Klētnieks
2019-09-02 7:38 ` Christoph Hellwig
2019-09-02 7:35 ` Christoph Hellwig
2019-09-02 15:25 ` Greg Kroah-Hartman
2019-09-02 19:00 ` Valdis Klētnieks
2019-09-02 19:06 ` Greg Kroah-Hartman
2019-09-08 10:50 ` 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=339527.1567309047@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=alexander.levin@microsoft.com \
--cc=david@fromorbit.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).