From: Ethan Carter Edwards <ethan@ethancedwards.com>
To: brauner@kernel.org, tytso@mit.edu, jack@suse.cz,
viro@zeniv.linux.org.uk
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
ernesto.mnd.fernandez@gmail.com, dan.carpenter@linaro.org,
sven@svenpeter.dev, ernesto@corellium.com,
gargaditya08@live.com, willy@infradead.org,
asahi@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-staging@lists.linux.dev,
Ethan Carter Edwards <ethan@ethancedwards.com>
Subject: [PATCH RFC v2 8/8] MAINTAINERS: apfs: add entry and relevant information
Date: Wed, 19 Mar 2025 20:13:57 -0400 [thread overview]
Message-ID: <20250319-apfs-v2-8-475de2e25782@ethancedwards.com> (raw)
In-Reply-To: <20250319-apfs-v2-0-475de2e25782@ethancedwards.com>
Add the APFS driver to staging/ and add myself as the maintainer.
Signed-off-by: Ethan Carter Edwards <ethan@ethancedwards.com>
---
MAINTAINERS | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 12852355bd66b2ca1841432b3e0d8c5856c62b9a..b4040e647e3ec6ae6b4723823fedff18c7a94544 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -683,6 +683,12 @@ F: Documentation/filesystems/afs.rst
F: fs/afs/
F: include/trace/events/afs.h
+APFS FILESYSTEM
+M: Ethan Carter Edwards <ethan@ethancedwards.com>
+L: linux-fsdevel@vger.kernel.org
+S: Maintained
+F: drivers/staging/apfs
+
AGPGART DRIVER
M: David Airlie <airlied@redhat.com>
L: dri-devel@lists.freedesktop.org
--
2.48.1
next prev parent reply other threads:[~2025-03-20 0:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 0:13 [RFC PATCH v2 0/8] staging: apfs: init APFS filesystem support Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 1/8] staging: apfs: init lzfse compression library for APFS Ethan Carter Edwards
2025-03-20 3:00 ` Aditya Garg
2025-03-20 0:13 ` [PATCH RFC v2 2/8] staging: apfs: init unicode.{c,h} Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 3/8] staging: apfs: init apfs_raw.h to handle on-disk structures Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 4/8] staging: apfs: init libzbitmap.{c,h} for decompression Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 5/8] staging: apfs: init APFS Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 6/8] staging: apfs: init build support for APFS Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 7/8] staging: apfs: init TODO and README.rst Ethan Carter Edwards
2025-03-20 0:13 ` Ethan Carter Edwards [this message]
2025-03-20 0:43 ` [RFC PATCH v2 0/8] staging: apfs: init APFS filesystem support Gao Xiang
2025-03-20 5:39 ` Dan Carpenter
2025-05-12 10:11 ` Subject: " Yangtao Li
2025-05-12 23:40 ` Ernesto A. Fernández
2025-05-13 4:13 ` Nick Chan
2025-05-13 10:43 ` Jan Kara
2025-05-13 11:41 ` Aditya Garg
2025-05-14 20:19 ` Ernesto A. Fernández
2025-05-15 5:08 ` Nick Chan
2025-05-15 16:00 ` Sven Peter
2025-05-20 5:08 ` Yangtao Li
2025-05-20 18:59 ` Ernesto A. Fernández
2025-05-21 10:14 ` Jan Kara
2025-05-21 16:27 ` Ernesto A. Fernández
2025-05-15 5:10 ` John Paul Adrian Glaubitz
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=20250319-apfs-v2-8-475de2e25782@ethancedwards.com \
--to=ethan@ethancedwards.com \
--cc=asahi@lists.linux.dev \
--cc=brauner@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=ernesto.mnd.fernandez@gmail.com \
--cc=ernesto@corellium.com \
--cc=gargaditya08@live.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sven@svenpeter.dev \
--cc=tytso@mit.edu \
--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