linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: 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
Subject: Re: Procedure questions - new filesystem driver..
Date: Tue, 9 Jul 2019 00:50:20 -0400	[thread overview]
Message-ID: <20190709045020.GB23646@mit.edu> (raw)
In-Reply-To: <21080.1562632662@turing-police>

On Mon, Jul 08, 2019 at 08:37:42PM -0400, Valdis Klētnieks wrote:
> I have an out-of-tree driver for the exfat file system that I beaten into shape
> for upstreaming. The driver works, and passes sparse and checkpatch (except
> for a number of line-too-long complaints).
> 
> Do you want this taken straight to the fs/ tree, or through drivers/staging?

How have you dealt with the patent claims which Microsoft has
asserted[1] on the exFAT file system design?

[1] https://www.microsoft.com/en-us/legal/intellectualproperty/mtl/exfat-licensing.aspx

I am not making any claims about the validity of Microsoft's patent
assertions on exFAT, one way or another.  But it might be a good idea
for some laywers from the Linux Foundation to render some legal advice
to their employees (namely Greg K-H and Linus Torvalds) regarding the
advisability of taking exFAT into the official Linux tree.

Personally, if Microsoft is going to be unfriendly about not wanting
others to use their file system technology by making patent claims,
why should we reward them by making their file system better by
improvings its interoperability?  (My personal opinion only.)

Cheers,

						- Ted


  parent reply	other threads:[~2019-07-09  4:51 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 [this message]
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
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=20190709045020.GB23646@mit.edu \
    --to=tytso@mit.edu \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).