From: "Pali Rohár" <pali.rohar@gmail.com>
To: Maurizio Lombardi <mlombard@redhat.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] fs: exFAT read-only driver GPL implementation by Paragon Software.
Date: Mon, 21 Oct 2019 13:13:57 +0200 [thread overview]
Message-ID: <20191021111357.q2lg2g43y7hrddqi@pali> (raw)
In-Reply-To: <0877502e-8369-9cfd-36e8-5a4798260cd4@redhat.com>
On Monday 21 October 2019 13:08:07 Maurizio Lombardi wrote:
> Dne 21.10.2019 v 12:54 Pali Rohár napsal(a):
> > Plus there is new version of
> > this out-of-tree Samsung's exfat driver called sdfat which can be found
> > in some Android phones.
>
> [...]
>
> >
> > About that one implementation from Samsung, which was recently merged
> > into staging tree, more people wrote that code is in horrible state and
> > probably it should not have been merged. That implementation has
> > all-one-one driver FAT12, FAT16, FAT32 and exFAT which basically
> > duplicate current kernel fs/fat code.
> >
> > Quick look at this Konstantin's patch, it looks like that code is not in
> > such bad state as staging one. It has only exFAT support (no FAT32) but
> > there is no write support (yet).
>
> But, AFAIK, Samsung is preparing a patch that will replace the current
> staging driver with their newer sdfat driver that also has write support.
>
> https://marc.info/?l=linux-fsdevel&m=156985252507812&w=2
Maurizio, thank you for reference! I have not caught this Samsung
activity yet! So we now we have +1 for count of exFAT drivers.
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2019-10-21 11:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 15:18 [PATCH] fs: exFAT read-only driver GPL implementation by Paragon Software Konstantin Komarov
2019-10-19 23:34 ` Pali Rohár
2019-10-22 17:13 ` [PATCH] " Konstantin Komarov
2019-10-20 18:08 ` [PATCH] fs: " Richard Weinberger
2019-10-21 10:54 ` Pali Rohár
2019-10-21 11:08 ` Maurizio Lombardi
2019-10-21 11:13 ` Pali Rohár [this message]
2019-10-21 11:31 ` Richard Weinberger
2019-10-21 11:11 ` Pali Rohár
2019-10-21 11:37 ` Maurizio Lombardi
2019-10-21 11:45 ` Pali Rohár
2019-10-21 12:01 ` Maurizio Lombardi
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=20191021111357.q2lg2g43y7hrddqi@pali \
--to=pali.rohar@gmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlombard@redhat.com \
--cc=richard.weinberger@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).