Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <4e8c0640-d781-877c-e6c5-ed5cc09443f6@gmail.com>
 <20210716114635.14797-1-papadakospan@gmail.com> <CAHk-=whfeq9gyPWK3yao6cCj7LKeU3vQEDGJ3rKDdcaPNVMQzQ@mail.gmail.com>
 <afd62ae457034c3fbc4f2d38408d359d@paragon-software.com>
In-Reply-To: <afd62ae457034c3fbc4f2d38408d359d@paragon-software.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri, 30 Jul 2021 10:23:51 -0700
Message-ID: <CAHk-=wjn4W-7ZbHrw08cWy=12DgheFUKLO5YLgG6in5TA5HxqQ@mail.gmail.com>
Subject: Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1)
To:     Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
        Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     "Leonidas P. Papadakos" <papadakospan@gmail.com>,
        "zajec5@gmail.com" <zajec5@gmail.com>,
        "Darrick J. Wong" <djwong@kernel.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Hans de Goede <hdegoede@redhat.com>,
        linux-fsdevel <linux-fsdevel@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Al Viro <viro@zeniv.linux.org.uk>,
        Matthew Wilcox <willy@infradead.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Fri, Jul 30, 2021 at 8:55 AM Konstantin Komarov
<almaz.alexandrovich@paragon-software.com> wrote:
>
> 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.

The one other thing I do want when there's big new pieces like this
being added is to ask you to make sure that everything is signed-off
properly, and that there is no internal confusion about the GPLv2
inside Paragon, and that any legal people etc are all aware of this
all and are on board. The last thing we want to see is some "oops, we
didn't mean to do this" brouhaha six months later.

I doubt that's an issue, considering how public this all has been, but
I just wanted to mention it just to be very obvious about it.

                  Linus