From: Richard Weinberger <richard.weinberger@gmail.com>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc: "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: Sun, 20 Oct 2019 20:08:20 +0200 [thread overview]
Message-ID: <CAFLxGvyFBGiDab4wxWidjRyDgWkHVfigVsHiRDB4swpB3G+hvQ@mail.gmail.com> (raw)
In-Reply-To: <453A1153-9493-4A04-BF66-CE6A572DEBDB@paragon-software.com>
On Sat, Oct 19, 2019 at 10:33 AM Konstantin Komarov
<almaz.alexandrovich@paragon-software.com> wrote:
>
> Recently exFAT filesystem specification has been made public by Microsoft (https://docs.microsoft.com/en-us/windows/win32/fileio/exfat-specification).
> Having decades of expertise in commercial file systems development, we at Paragon Software GmbH are very excited by Microsoft's decision and now want to make our contribution to the Open Source Community by providing our implementation of exFAT Read-Only (yet!) fs implementation for the Linux Kernel.
> We are about to prepare the Read-Write support patch as well.
> 'fs/exfat' is implemented accordingly to standard Linux fs development approach with no use/addition of any custom API's.
> To divide our contribution from 'drivers/staging' submit of Aug'2019, our Kconfig key is "EXFAT_RO_FS"
How is this driver different from the driver in drivers/staging?
With the driver in staging and the upcoming driver from Samsung this
is driver number
three for exfat. ;-\
--
Thanks,
//richard
next prev parent reply other threads:[~2019-10-20 18:08 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 ` Richard Weinberger [this message]
2019-10-21 10:54 ` [PATCH] fs: " Pali Rohár
2019-10-21 11:08 ` Maurizio Lombardi
2019-10-21 11:13 ` Pali Rohár
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=CAFLxGvyFBGiDab4wxWidjRyDgWkHVfigVsHiRDB4swpB3G+hvQ@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).