From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
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>,
"ntfs3@lists.linux.dev" <ntfs3@lists.linux.dev>
Subject: RE: Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1)
Date: Fri, 13 Aug 2021 16:11:10 +0000 [thread overview]
Message-ID: <a9114805f777461eac6fbb0e8e5c46f6@paragon-software.com> (raw)
In-Reply-To: <CAHk-=wjn4W-7ZbHrw08cWy=12DgheFUKLO5YLgG6in5TA5HxqQ@mail.gmail.com>
> 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 <sfr@canb.auug.org.au>
> Cc: Leonidas P. Papadakos <papadakospan@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>
> Subject: Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1)
>
> 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.
>
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.
> 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
Indeed, there is no internal confusion about the GPLv2 and we mean to make this contribution.
Best regards,
Konstantin.
next prev parent reply other threads:[~2021-08-13 16:11 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 10:45 [GIT PULL] vboxsf fixes for 5.14-1 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
2021-07-30 15:55 ` Konstantin Komarov
2021-07-30 17:23 ` Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1) Linus Torvalds
2021-08-13 16:11 ` Konstantin Komarov [this message]
2021-08-15 20:32 ` Stephen Rothwell
2021-08-16 3:00 ` Kari Argillander
2021-09-02 21:55 ` Linus Torvalds
2021-08-03 22:48 ` [GIT PULL] vboxsf fixes for 5.14-1 Theodore Ts'o
2021-08-03 23:44 ` Matthew Wilcox
2021-08-04 0:04 ` Theodore Ts'o
2021-08-04 0:10 ` Linus Torvalds
2021-08-04 0:49 ` Theodore Ts'o
2021-08-04 1:03 ` Darrick J. Wong
2021-08-04 6:38 ` Kari Argillander
2021-08-04 16:30 ` Theodore Ts'o
2021-08-05 15:48 ` Konstantin Komarov
2021-08-10 7:02 ` Darrick J. Wong
2021-09-02 22:09 ` NTFS testing (was: " Szabolcs Szakacsits
2021-09-03 17:48 ` Eric Biggers
2021-09-03 21:17 ` Szabolcs Szakacsits
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
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=a9114805f777461eac6fbb0e8e5c46f6@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=djwong@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=papadakospan@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=zajec5@gmail.com \
/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).