Hi Konstantin,

On Fri, 13 Aug 2021 16:11:10 +0000 Konstantin Komarov [off-list ref] wrote:

quoted

From: Linus Torvalds <torvalds@linux-foundation.org>
Sent: Friday, July 30, 2021 8:24 PM
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>; Stephen Rothwell <redacted>
Cc: Leonidas P. Papadakos <redacted>; zajec5@gmail.com; Darrick J. Wong <djwong@kernel.org>; Greg Kroah-
Hartman [off-list ref]; Hans de Goede [off-list ref]; linux-fsdevel [off-list ref];
Linux Kernel Mailing List [off-list ref]; Al Viro [off-list ref]; Matthew Wilcox [off-list ref]
Subject: Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1)

On Fri, Jul 30, 2021 at 8:55 AM Konstantin Komarov
[off-list ref] wrote:  

quoted

We've just sent the 27th patch series which fixes to the buildability against
current linux-next. And we'll need several days to prepare a proper pull request
before sending it to you.  

Well, I won't pull until the next merge window opens anyway (about a
month away). But it would be good to have your tree in linux-next for
at least a couple of weeks before that happens.

Added Stephen to the participants list as a heads-up for him - letting
him know where to fetch the git tree from will allow that to happen if
you haven't done so already.
  

Thanks for this clarification, Linus!
Stephen, please find the tree here:
https://github.com/Paragon-Software-Group/linux-ntfs3.git
It is the fork from 5.14-rc5 tag with ntfs3 patches applied.
Also, the latest changes
- fix some generic/XYZ xfstests, which were discussed
with Theodore, Darrick and others
- updates the MAINTAINERS with mailing list (also added to CC here) and scm tree link.

Please let me know if additional changes requred to get fetched into linux-next.

Added from today.  It looks good, we will see how it goes when integrated/built.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

-- 
Cheers,
Stephen Rothwell