From: Christian Brauner <brauner@kernel.org>
To: Zorro Lang <zlang@kernel.org>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
ceph-devel@vger.kernel.org, linux-cifs@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
ocfs2-devel@oss.oracle.com, linux-unionfs@vger.kernel.org,
jack@suse.com, linux-xfs@vger.kernel.org, fdmanana@suse.com,
ebiggers@google.com, amir73il@gmail.com, djwong@kernel.org,
anand.jain@oracle.com
Subject: Re: [PATCH 3/5] fstests/MAINTAINERS: add supported mailing list
Date: Wed, 5 Apr 2023 09:49:27 +0200 [thread overview]
Message-ID: <20230405-bazillus-nanotechnologie-a8cf619d8454@brauner> (raw)
In-Reply-To: <20230404171411.699655-4-zlang@kernel.org>
On Wed, Apr 05, 2023 at 01:14:09AM +0800, Zorro Lang wrote:
> The fstests supports different kind of fs testing, better to cc
> specific fs mailing list for specific fs testing, to get better
> reviewing points. So record these mailing lists and files related
> with them in MAINTAINERS file.
>
> Signed-off-by: Zorro Lang <zlang@kernel.org>
> ---
>
> If someone mailing list doesn't want to be in cc list of related fstests
> patch, please reply this email, I'll remove that line.
>
> Or if I missed someone mailing list, please feel free to tell me.
>
> Thanks,
> Zorro
>
> MAINTAINERS | 77 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 77 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 09b1a5a3..620368cb 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -107,6 +107,83 @@ Maintainers List
> should send patch to fstests@ at least. Other relevant mailing list
> or reviewer or co-maintainer can be in cc list.
>
> +BTRFS
> +L: linux-btrfs@vger.kernel.org
> +S: Supported
> +F: tests/btrfs/
> +F: common/btrfs
> +
> +CEPH
> +L: ceph-devel@vger.kernel.org
> +S: Supported
> +F: tests/ceph/
> +F: common/ceph
> +
> +CIFS
> +L: linux-cifs@vger.kernel.org
> +S: Supported
> +F: tests/cifs
> +
> +EXT4
> +L: linux-ext4@vger.kernel.org
> +S: Supported
> +F: tests/ext4/
> +F: common/ext4
> +
> +F2FS
> +L: linux-f2fs-devel@lists.sourceforge.net
> +S: Supported
> +F: tests/f2fs/
> +F: common/f2fs
> +
> +FSVERITY
> +L: fsverity@lists.linux.dev
> +S: Supported
> +F: common/verity
> +
> +FSCRYPT
> +L: linux-fscrypt@vger.kernel.org
> +S: Supported
> +F: common/encrypt
> +
> +FS-IDMAPPED
> +L: linux-fsdevel@vger.kernel.org
> +S: Supported
> +F: src/vfs/
Same suggestion as earlier, make that section VFS as it covers generic
functionality,
Acked-by: Christian Brauner <brauner@kernel.org>
next prev parent reply other threads:[~2023-04-05 7:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 17:14 [RFC PATCH 0/5] fstests specific MAINTAINERS file Zorro Lang
2023-04-04 17:14 ` [PATCH 1/5] fstests: add MAINTAINERS and get_maintainer.pl files Zorro Lang
2023-04-04 23:21 ` Darrick J. Wong
2023-04-06 20:10 ` John Hubbard
2023-04-04 17:14 ` [PATCH 2/5] tools/get_maintainer.pl: remove penguin chiefs Zorro Lang
2023-04-04 17:14 ` [PATCH 3/5] fstests/MAINTAINERS: add supported mailing list Zorro Lang
2023-04-04 22:16 ` Eric Biggers
2023-04-04 23:22 ` Darrick J. Wong
2023-04-05 14:02 ` Zorro Lang
2023-04-04 23:21 ` Darrick J. Wong
2023-04-05 4:04 ` Steve French
2023-04-05 7:49 ` Christian Brauner [this message]
2023-04-05 9:52 ` Jan Kara
2023-04-06 0:25 ` Xiubo Li
2023-04-06 1:53 ` [f2fs-dev] " Chao Yu
2023-04-04 17:14 ` [PATCH 4/5] fstests/MAINTAINERS: add some specific reviewers Zorro Lang
2023-04-04 23:23 ` Darrick J. Wong
2023-04-05 7:29 ` Amir Goldstein
2023-04-05 7:47 ` Christian Brauner
2023-04-06 5:02 ` Zorro Lang
2023-04-06 7:49 ` Christian Brauner
2023-04-04 17:14 ` [PATCH 5/5] fstests/MAINTAINERS: add a co-maintainer for btrfs testing part Zorro Lang
2023-04-04 23:26 ` Darrick J. Wong
2023-04-06 14:17 ` David Sterba
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=20230405-bazillus-nanotechnologie-a8cf619d8454@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=anand.jain@oracle.com \
--cc=ceph-devel@vger.kernel.org \
--cc=djwong@kernel.org \
--cc=ebiggers@google.com \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=jack@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=zlang@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).