From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: KY Srinivasan <kys@microsoft.com>
Cc: Matthew Wilcox <willy@infradead.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Sasha Levin <sashal@kernel.org>
Subject: Re: exfat filesystem
Date: Tue, 09 Jul 2019 12:50:43 -0400 [thread overview]
Message-ID: <24605.1562691043@turing-police> (raw)
In-Reply-To: <SN6PR2101MB10726033399AEA1D0BD22067A0F10@SN6PR2101MB1072.namprd21.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
On Tue, 09 Jul 2019 16:39:31 -0000, KY Srinivasan said:
> Let me dig up the details here.
In case this helps clarify the chain of events, the code in question
is the Samsung code mentioned here, updated to 5.2 kernel....
"We know that Microsoft has done patent troll shakedowns in the past on Linux
products related to the exfat filesystem. While we at Conservancy were
successful in getting the code that implements exfat for Linux released under
GPL (by Samsung), that code has not been upstreamed into Linux. So, Microsoft
has not included any patents they might hold on exfat into the patent
non-aggression pact."
https://sfconservancy.org/blog/2018/oct/10/microsoft-oin-exfat/
(Link in that para points here):
https://sfconservancy.org/news/2013/aug/16/exfat-samsung/
[-- Attachment #2: Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-07-09 16:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 0:37 Procedure questions - new filesystem driver Valdis Klētnieks
2019-07-09 0:52 ` Al Viro
2019-07-09 0:58 ` Valdis Klētnieks
2019-07-09 4:50 ` Theodore Ts'o
2019-07-09 11:21 ` Matthew Wilcox
2019-07-09 15:30 ` Theodore Ts'o
2019-07-09 15:48 ` exfat filesystem Matthew Wilcox
2019-07-09 16:15 ` James Bottomley
2019-07-09 16:21 ` Valdis Klētnieks
2019-07-09 16:37 ` Sasha Levin
2019-07-09 17:03 ` James Bottomley
2019-07-09 16:39 ` KY Srinivasan
2019-07-09 16:50 ` Valdis Klētnieks [this message]
2019-07-09 17:13 ` KY Srinivasan
2019-07-09 16:46 ` Theodore Ts'o
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=24605.1562691043@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kys@microsoft.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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).