[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 5 Apr 2023 01:14:11 +0800
From: Zorro Lang <zlang@...nel.org>
To: fstests@...r.kernel.org
Cc: linux-btrfs@...r.kernel.org, ceph-devel@...r.kernel.org,
linux-cifs@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net,
linux-fsdevel@...r.kernel.org, linux-nfs@...r.kernel.org,
ocfs2-devel@....oracle.com, linux-unionfs@...r.kernel.org,
jack@...e.com, linux-xfs@...r.kernel.org, fdmanana@...e.com,
ebiggers@...gle.com, brauner@...nel.org, amir73il@...il.com,
djwong@...nel.org, anand.jain@...cle.com
Subject: [PATCH 5/5] fstests/MAINTAINERS: add a co-maintainer for btrfs testing part
Darrick J. Wong would like to nominate Anand Jain to help more on
btrfs testing part (tests/btrfs and common/btrfs). He would like to
be a co-maintainer of btrfs part, will help to review and test
fstests btrfs related patches, and I might merge from him if there's
big patchset. So CC him besides send to fstests@ list, when you have
a btrfs fstests patch.
Signed-off-by: Zorro Lang <zlang@...nel.org>
---
Please btrfs list help to review this change, if you agree (or no objection),
then I'll push this change.
A co-maintainer will do:
1) Review patches are related with him.
2) Merge and test patches in his local git repo, and give the patch an ACK.
3) Maintainer will trust the ack from co-maintainer more (might merge directly).
4) Maintainer might merge from co-maintainer when he has a big patchset wait for
merging.
Thanks,
Zorro
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 0ad12a38..9fc6c6b5 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -108,6 +108,7 @@ Maintainers List
or reviewer or co-maintainer can be in cc list.
BTRFS
+M: Anand Jain <anand.jain@...cle.com>
R: Filipe Manana <fdmanana@...e.com>
L: linux-btrfs@...r.kernel.org
S: Supported
--
2.39.2
Powered by blists - more mailing lists