From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: <linux-fsdevel@vger.kernel.org>
Cc: <viro@zeniv.linux.org.uk>, <linux-kernel@vger.kernel.org>,
<pali@kernel.org>, <dsterba@suse.cz>, <aaptel@suse.com>,
<willy@infradead.org>, <rdunlap@infradead.org>, <joe@perches.com>,
<mark@harmstone.com>,
Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Subject: [PATCH v3 10/10] fs/ntfs3: Add MAINTAINERS
Date: Fri, 28 Aug 2020 07:39:38 -0700 [thread overview]
Message-ID: <20200828143938.102889-11-almaz.alexandrovich@paragon-software.com> (raw)
In-Reply-To: <20200828143938.102889-1-almaz.alexandrovich@paragon-software.com>
This adds MAINTAINERS
Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
---
MAINTAINERS | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3b186ade3597..b3db537a8310 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -12354,6 +12354,13 @@ T: git git://git.kernel.org/pub/scm/linux/kernel/git/aia21/ntfs.git
F: Documentation/filesystems/ntfs.rst
F: fs/ntfs/
+NTFS3 FILESYSTEM
+M: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
+S: Supported
+W: http://www.paragon-software.com/
+F: Documentation/filesystems/ntfs3.rst
+F: fs/ntfs3/
+
NUBUS SUBSYSTEM
M: Finn Thain <fthain@telegraphics.com.au>
L: linux-m68k@lists.linux-m68k.org
--
2.25.2
next prev parent reply other threads:[~2020-08-28 14:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 14:39 [PATCH v3 00/10] NTFS read-write driver GPL implementation by Paragon Software Konstantin Komarov
2020-08-28 14:39 ` [PATCH v3 01/10] fs/ntfs3: Add headers and misc files Konstantin Komarov
2020-08-28 14:39 ` [PATCH v3 02/10] fs/ntfs3: Add initialization of super block Konstantin Komarov
2020-09-04 12:06 ` Pali Rohár
2020-09-11 16:59 ` Konstantin Komarov
2020-08-28 14:39 ` [PATCH v3 03/10] fs/ntfs3: Add bitmap Konstantin Komarov
2020-08-28 14:39 ` [PATCH v3 04/10] fs/ntfs3: Add file operations and implementation Konstantin Komarov
2020-08-28 15:45 ` Al Viro
2020-09-04 12:41 ` Konstantin Komarov
2020-08-28 15:55 ` Al Viro
2020-09-04 12:49 ` Konstantin Komarov
2020-09-04 11:50 ` Pali Rohár
2020-09-11 16:52 ` Konstantin Komarov
2020-09-21 13:36 ` Pali Rohár
2020-09-22 10:26 ` Aurélien Aptel
2020-09-25 16:39 ` Konstantin Komarov
2020-08-28 14:39 ` [PATCH v3 05/10] fs/ntfs3: Add attrib operations Konstantin Komarov
2020-08-28 16:14 ` Mark Harmstone
2020-08-28 14:39 ` [PATCH v3 06/10] fs/ntfs3: Add compression Konstantin Komarov
2020-08-28 14:39 ` [PATCH v3 07/10] fs/ntfs3: Add NTFS journal Konstantin Komarov
2020-08-28 14:39 ` [PATCH v3 08/10] fs/ntfs3: Add Kconfig, Makefile and doc Konstantin Komarov
2020-08-28 14:39 ` [PATCH v3 09/10] fs/ntfs3: Add NTFS3 in fs/Kconfig and fs/Makefile Konstantin Komarov
2020-09-01 0:37 ` kernel test robot
2020-09-01 4:45 ` kernel test robot
2020-08-28 14:39 ` Konstantin Komarov [this message]
2020-08-29 11:31 ` [PATCH v3 00/10] NTFS read-write driver GPL implementation by Paragon Software Nikolay Borisov
2020-09-04 12:55 ` Konstantin Komarov
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=20200828143938.102889-11-almaz.alexandrovich@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=aaptel@suse.com \
--cc=dsterba@suse.cz \
--cc=joe@perches.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@harmstone.com \
--cc=pali@kernel.org \
--cc=rdunlap@infradead.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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).