[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ed518871bf6182bb7d9a2b95074985cf8af1d5c4.camel@perches.com>
Date: Fri, 21 Aug 2020 12:21:12 -0700
From: Joe Perches <joe@...ches.com>
To: Konstantin Komarov <almaz.alexandrovich@...agon-software.com>,
"viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>
Cc: Pali Rohár <pali@...nel.org>
Subject: Re: [PATCH v2 00/10] fs: NTFS read-write driver GPL implementation
by Paragon Software.
On Fri, 2020-08-21 at 16:24 +0000, Konstantin Komarov wrote:
> This patch adds NTFS Read-Write driver to fs/ntfs3.
Thanks.
Proper ntfs read/write support will be great addition.
Trivia:
If this patchset is submitted again with a new version,
please use something like "git format-patch --cover-letter"
and "git send-email" so all parts of the patches and replies
have the a single message thread to follow.
That will add an "in-reply-to" header of the 0/m patch
message-id to all n/m parts.
One style oddity I noticed is the use of goto labels in
favor of if block indentation. It's not terrible style,
just unusual for kernel code.
Powered by blists - more mailing lists