From: Christoph Hellwig <hch@lst.de>
To: djwong@kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH] drop me from MAINTAINERS for iomap
Date: Tue, 20 Jun 2023 07:29:33 +0200 [thread overview]
Message-ID: <20230620052933.711180-1-hch@lst.de> (raw)
As Darrick prefers to micro-manage this without looking at my input
for code I wrote and then complain about getting burned out by that
I might as well drop myself from the maintainers file.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index f794002a192e24..9c4a5572ae3382 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10813,7 +10813,6 @@ S: Maintained
F: drivers/net/ethernet/sgi/ioc3-eth.c
IOMAP FILESYSTEM LIBRARY
-M: Christoph Hellwig <hch@infradead.org>
M: Darrick J. Wong <djwong@kernel.org>
L: linux-xfs@vger.kernel.org
L: linux-fsdevel@vger.kernel.org
--
2.39.2
next reply other threads:[~2023-06-20 5:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 5:29 Christoph Hellwig [this message]
2023-06-28 17:56 ` [PATCH] drop me from MAINTAINERS for iomap Darrick J. Wong
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=20230620052933.711180-1-hch@lst.de \
--to=hch@lst.de \
--cc=djwong@kernel.org \
--cc=linux-fsdevel@vger.kernel.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).