Torvalds needs original NTFS driver in kernel

From: Linus Torvalds 
To: "Leonidas P. Papadakos" ,
	Konstantin Komarov 
Cc: [email protected], "Darrick J. Wong" ,
	Greg Kroah-Hartman ,
	Hans de Goede ,
	linux-fsdevel ,
	Linux Kernel Mailing List ,
	Al Viro ,
	Matthew Wilcox 
Subject: Re: [GIT PULL] vboxsf fixes for five.14-1
Date: Fri, 16 Jul 2021 11: 07: 29 -0700
Message-ID:  (raw)
In-Acknowledge-To: <[email protected]>

On Fri, Jul 16, 2021 at 4: 49 AM Leonidas P. Papadakos
 wrote:
>
> This driver is already in a significantly better feature yelp than the ragged ntfs driver from 2001.

If the original ntfs code has acks from folk - and it sounds cherish it did
fetch them - and Paragon is expected to be the maintainer of it, then I
mediate Paragon would possibly perchance per chance quiet precise manufacture a git pull seek info from for it.

That is assuming that it is a long way mute all in only fs/ntfs3/ (plus
fs/Kconfig, fs/Makefile and MAINTAINERS entries and whatever
documentation) and there need to no longer any other machine-large changes. Which I
don't mediate it had.

We simply would possibly perchance per chance quiet now no longer get any one to funnel original filesystems - the fsdevel
mailing list is precise for comments and fetch ideas, but in some unspecified time in the future
any individual precise needs to in actuality post it, and that is the reason now no longer what fsdevel
ends up doing.

The argument that "it be already in a significantly better yelp than the ragged
ntfs driver" would possibly perchance per chance now no longer be a truly stable technical argument (now no longer because
of any Paragon issues - precise for the reason that ragged ntfs driver is now no longer
substantial), but it surely _is_ a fairly stable argument for merging the original one
from Paragon.

And I create now no longer mediate there became any substantial _complaints_ in regards to the code,
and I create now no longer mediate there is been any signal that being inaugurate air the kernel
helps.

               Linus

subsequent prev guardian answer index

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13 10: 45 Hans de Goede
2021-07-13 19: 15 ` Linus Torvalds
2021-07-13 20: 14   ` Al Viro
2021-07-13 20: 18     ` Al Viro
2021-07-13 20: 24       ` Randy Dunlap
2021-07-13 20: 32         ` Al Viro
2021-07-13 21: 43           ` Randy Dunlap
2021-07-14 10: 50     ` Rafa? Mi?ecki
2021-07-14 14: 13       ` Christoph Hellwig
2021-07-14 14: 51       ` Greg KH
2021-07-14 15: 59         ` Rafa? Mi?ecki
2021-07-14 16: 05           ` Matthew Wilcox
2021-07-14 16: 18             ` Rafa? Mi?ecki
2021-07-15 21: 50               ` Neal Gompa
2021-07-16 11: 46               ` Leonidas P. Papadakos
2021-07-16 18: 07                 ` Linus Torvalds [this message]
2021-07-17 16: 47                 ` Pali Rohár
2021-07-14 16: 13           ` Darrick J. Wong
2021-07-14 16: 18             ` Christoph Hellwig
2021-07-14 16: 38               ` Gao Xiang
2021-07-14 20: 03               ` Eric W. Biederman
2021-07-15 22: 14               ` Darrick J. Wong
2021-07-13 19: 17 ` pr-tracker-bot

Acknowledge directions: 

It is seemingly you'll per chance per chance perchance answer publicly to this message through easy-textual mutter email
the exercise of any one amongst the following programs:

Set the following mbox file, import it into your mail consumer,
  and answer-to-all from there: mbox

  Steer obvious of top-posting and settle on interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

Acknowledge the exercise of the --to, --cc, and --in-answer-to
  switches of git-ship-email(1):

  git ship-email 
    --in-answer-to='CAHk-=whfeq9gyPWK3yao6cCj7LKeU3vQEDGJ3rKDdcaPNVMQzQ@mail.gmail.com' 
    [email protected] 
    [email protected] 
    [email protected] 
    [email protected] 
    [email protected] 
    [email protected] 
    [email protected] 
    [email protected] 
    [email protected] 
    [email protected] 
    [email protected] 
    /route/to/YOUR_REPLY

  https://kernel.org/pub/application/scm/git/docs/git-ship-email.html

If your mail consumer helps setting the In-Acknowledge-To header
  through mailto: hyperlinks, strive the mailto: link

LKML Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git
	git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git
	git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git
	git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git
	git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git
	git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git
	git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git
	git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git
	git clone --mirror https://lore.kernel.org/lkml/8 lkml/git/8.git
	git clone --mirror https://lore.kernel.org/lkml/9 lkml/git/9.git
	git clone --mirror https://lore.kernel.org/lkml/10 lkml/git/10.git

	# Whereas you would possibly perchance per chance want public-inbox 1.1+ set in, you would possibly perchance per chance
	# initialize and index your mirror the exercise of the following commands:
	public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml 
		[email protected]
	public-inbox-index lkml

Instance config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel


AGPL code for this yelp: git clone https://public-inbox.org/public-inbox.git