linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: "Theodore Ts'o" <tytso@mit.edu>,
	"Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
	"Alexander Viro" <viro@zeniv.linux.org.uk>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	devel@driverdev.osuosl.org, kys@microsoft.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: exfat filesystem
Date: Tue, 9 Jul 2019 08:48:34 -0700	[thread overview]
Message-ID: <20190709154834.GJ32320@bombadil.infradead.org> (raw)
In-Reply-To: <20190709153039.GA3200@mit.edu>

On Tue, Jul 09, 2019 at 11:30:39AM -0400, Theodore Ts'o wrote:
> On Tue, Jul 09, 2019 at 04:21:36AM -0700, Matthew Wilcox wrote:
> > How does
> > https://www.zdnet.com/article/microsoft-open-sources-its-entire-patent-portfolio/
> > change your personal opinion?
> 
> According to SFC's legal analysis, Microsoft joining the OIN doesn't
> mean that the eXFAT patents are covered, unless *Microsoft*
> contributes the code to the Linux usptream kernel.  That's because the
> OIN is governed by the Linux System Definition, and until MS
> contributes code which covered by the exFAT patents, it doesn't count.
> 
> For more details:
> 
> https://sfconservancy.org/blog/2018/oct/10/microsoft-oin-exfat/
> 
> (This is not legal advice, and I am not a lawyer.)

Interesting analysis.  It seems to me that the correct forms would be
observed if someone suitably senior at Microsoft accepted the work from
Valdis and submitted it with their sign-off.  KY, how about it?

  reply	other threads:[~2019-07-09 15:48 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       ` Matthew Wilcox [this message]
2019-07-09 16:15         ` exfat filesystem 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
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=20190709154834.GJ32320@bombadil.infradead.org \
    --to=willy@infradead.org \
    --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=valdis.kletnieks@vt.edu \
    --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).