From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: xfs <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Dave Chinner <david@fromorbit.com>,
Eric Sandeen <sandeen@redhat.com>
Subject: [RFC PATCH] iomap: take responsibility for the filesystem iomap code
Date: Wed, 19 Dec 2018 21:36:22 -0800 [thread overview]
Message-ID: <20181220053622.GD27176@magnolia> (raw)
From: Darrick J. Wong <darrick.wong@oracle.com>
XFS is the primary user of the filesystem iomap code, so we (the XFS
community, specifically) will explicitly take responsibility for its
maintenance.
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
---
Just floating this as a test balloon. Would like at acks from at least
Dave and Christoph since they wrote most of the fs iomap code.
---
MAINTAINERS | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8119141a926f..a36a88a72423 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -16518,6 +16518,16 @@ L: alsa-devel@alsa-project.org (moderated for non-subscribers)
S: Supported
F: sound/xen/*
+IOMAP FILESYSTEM LIBRARY
+M: linux-xfs@vger.kernel.org
+M: linux-fsdevel@vger.kernel.org
+L: linux-xfs@vger.kernel.org
+L: linux-fsdevel@vger.kernel.org
+T: git git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
+S: Supported
+F: fs/iomap.c
+F: include/linux/iomap.h
+
XFS FILESYSTEM
M: Darrick J. Wong <darrick.wong@oracle.com>
M: linux-xfs@vger.kernel.org
next reply other threads:[~2018-12-20 5:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 5:36 Darrick J. Wong [this message]
2018-12-20 7:08 ` [RFC PATCH] iomap: take responsibility for the filesystem iomap code Christoph Hellwig
2018-12-20 7:27 ` Amir Goldstein
2018-12-20 19:04 ` [PATCH v2] " Darrick J. Wong
2018-12-20 19:07 ` Al Viro
2018-12-21 22:05 ` Dave Chinner
2018-12-24 0:37 ` [PATCH v3] " Darrick J. Wong
2018-12-27 8:08 ` Christoph Hellwig
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=20181220053622.GD27176@magnolia \
--to=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.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).