From: Zorro Lang <zlang@redhat.com> To: Eric Biggers <ebiggers@kernel.org> Cc: Zorro Lang <zlang@kernel.org>, fstests@vger.kernel.org, brauner@kernel.org, linux-cifs@vger.kernel.org, linux-nfs@vger.kernel.org, djwong@kernel.org, amir73il@gmail.com, linux-unionfs@vger.kernel.org, anand.jain@oracle.com, linux-f2fs-devel@lists.sourceforge.net, linux-xfs@vger.kernel.org, fdmanana@suse.com, jack@suse.com, linux-fsdevel@vger.kernel.org, ceph-devel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org Subject: Re: [PATCH 3/5] fstests/MAINTAINERS: add supported mailing list Date: Wed, 5 Apr 2023 22:02:02 +0800 [thread overview] Message-ID: <20230405140202.bdp3lzgross2cjbt@zlang-mailbox> (raw) In-Reply-To: <20230404221653.GC1893@sol.localdomain> On Tue, Apr 04, 2023 at 03:16:53PM -0700, Eric Biggers wrote: > Hi Zorro, > > On Wed, Apr 05, 2023 at 01:14:09AM +0800, Zorro Lang wrote: > > +FSVERITY > > +L: fsverity@lists.linux.dev > > +S: Supported > > +F: common/verity > > + > > +FSCRYPT > > +L: linux-fscrypt@vger.kernel.org > > +S: Supported > > +F: common/encrypt > > Most of the encrypt and verity tests are in tests/generic/ and are in the > 'encrypt' or 'verity' test groups. > > These file patterns only pick up the common files, not the actual tests. > > Have you considered adding a way to specify maintainers for a test group? > Something like: > > G: encrypt > > and > > G: verity Good idea! Let's check if this patchset is acceptable by most of you, then I'll think about how to add this feature later. Thanks, Zorro > > - Eric >
WARNING: multiple messages have this Message-ID (diff)
From: Zorro Lang <zlang@redhat.com> To: Eric Biggers <ebiggers@kernel.org> Cc: linux-cifs@vger.kernel.org, brauner@kernel.org, linux-ext4@vger.kernel.org, Zorro Lang <zlang@kernel.org>, djwong@kernel.org, amir73il@gmail.com, linux-nfs@vger.kernel.org, fstests@vger.kernel.org, linux-unionfs@vger.kernel.org, linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, anand.jain@oracle.com, jack@suse.com, fdmanana@suse.com, ceph-devel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-btrfs@vger.kernel.org Subject: Re: [f2fs-dev] [PATCH 3/5] fstests/MAINTAINERS: add supported mailing list Date: Wed, 5 Apr 2023 22:02:02 +0800 [thread overview] Message-ID: <20230405140202.bdp3lzgross2cjbt@zlang-mailbox> (raw) In-Reply-To: <20230404221653.GC1893@sol.localdomain> On Tue, Apr 04, 2023 at 03:16:53PM -0700, Eric Biggers wrote: > Hi Zorro, > > On Wed, Apr 05, 2023 at 01:14:09AM +0800, Zorro Lang wrote: > > +FSVERITY > > +L: fsverity@lists.linux.dev > > +S: Supported > > +F: common/verity > > + > > +FSCRYPT > > +L: linux-fscrypt@vger.kernel.org > > +S: Supported > > +F: common/encrypt > > Most of the encrypt and verity tests are in tests/generic/ and are in the > 'encrypt' or 'verity' test groups. > > These file patterns only pick up the common files, not the actual tests. > > Have you considered adding a way to specify maintainers for a test group? > Something like: > > G: encrypt > > and > > G: verity Good idea! Let's check if this patchset is acceptable by most of you, then I'll think about how to add this feature later. Thanks, Zorro > > - Eric > _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2023-04-05 14:17 UTC|newest] Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-04 17:14 [f2fs-dev] [RFC PATCH 0/5] fstests specific MAINTAINERS file Zorro Lang 2023-04-04 17:14 ` [Ocfs2-devel] " Zorro Lang via Ocfs2-devel 2023-04-04 17:14 ` Zorro Lang 2023-04-04 17:14 ` [PATCH 1/5] fstests: add MAINTAINERS and get_maintainer.pl files Zorro Lang 2023-04-04 17:14 ` [Ocfs2-devel] " Zorro Lang via Ocfs2-devel 2023-04-04 17:14 ` [f2fs-dev] " Zorro Lang 2023-04-04 23:21 ` Darrick J. Wong 2023-04-04 23:21 ` Darrick J. Wong 2023-04-04 23:21 ` [Ocfs2-devel] " Darrick J. Wong via Ocfs2-devel 2023-04-06 20:10 ` John Hubbard via Ocfs2-devel 2023-04-06 20:10 ` [f2fs-dev] " John Hubbard via Linux-f2fs-devel 2023-04-06 20:10 ` John Hubbard 2023-04-06 20:48 ` Zorro Lang 2023-04-06 20:52 ` John Hubbard 2023-04-08 4:14 ` Zorro Lang 2023-04-08 4:54 ` John Hubbard 2023-04-04 17:14 ` [f2fs-dev] [PATCH 2/5] tools/get_maintainer.pl: remove penguin chiefs Zorro Lang 2023-04-04 17:14 ` [Ocfs2-devel] " Zorro Lang via Ocfs2-devel 2023-04-04 17:14 ` Zorro Lang 2023-04-04 17:14 ` [f2fs-dev] [PATCH 3/5] fstests/MAINTAINERS: add supported mailing list Zorro Lang 2023-04-04 17:14 ` [Ocfs2-devel] " Zorro Lang via Ocfs2-devel 2023-04-04 17:14 ` Zorro Lang 2023-04-04 22:16 ` [f2fs-dev] " Eric Biggers 2023-04-04 22:16 ` Eric Biggers 2023-04-04 22:16 ` [Ocfs2-devel] " Eric Biggers via Ocfs2-devel 2023-04-04 23:22 ` [f2fs-dev] " Darrick J. Wong 2023-04-04 23:22 ` Darrick J. Wong 2023-04-04 23:22 ` [Ocfs2-devel] " Darrick J. Wong via Ocfs2-devel 2023-04-05 14:02 ` Zorro Lang [this message] 2023-04-05 14:02 ` Zorro Lang 2023-04-04 23:21 ` [f2fs-dev] " Darrick J. Wong 2023-04-04 23:21 ` Darrick J. Wong 2023-04-04 23:21 ` [Ocfs2-devel] " Darrick J. Wong via Ocfs2-devel 2023-04-05 4:04 ` [f2fs-dev] " Steve French 2023-04-05 4:04 ` Steve French 2023-04-05 4:04 ` [Ocfs2-devel] " Steve French via Ocfs2-devel 2023-04-05 7:49 ` [f2fs-dev] " Christian Brauner 2023-04-05 7:49 ` Christian Brauner 2023-04-05 7:49 ` [Ocfs2-devel] " Christian Brauner via Ocfs2-devel 2023-04-05 9:52 ` [f2fs-dev] " Jan Kara 2023-04-05 9:52 ` Jan Kara 2023-04-05 9:52 ` [Ocfs2-devel] " Jan Kara via Ocfs2-devel 2023-04-06 0:25 ` [f2fs-dev] " Xiubo Li 2023-04-06 0:25 ` Xiubo Li 2023-04-06 0:25 ` [Ocfs2-devel] " Xiubo Li via Ocfs2-devel 2023-04-06 1:53 ` [f2fs-dev] " Chao Yu 2023-04-06 1:53 ` Chao Yu 2023-04-06 1:53 ` [Ocfs2-devel] " Chao Yu via Ocfs2-devel 2023-04-04 17:14 ` [f2fs-dev] [PATCH 4/5] fstests/MAINTAINERS: add some specific reviewers Zorro Lang 2023-04-04 17:14 ` [Ocfs2-devel] " Zorro Lang via Ocfs2-devel 2023-04-04 17:14 ` Zorro Lang 2023-04-04 23:23 ` [f2fs-dev] " Darrick J. Wong 2023-04-04 23:23 ` Darrick J. Wong 2023-04-04 23:23 ` [Ocfs2-devel] " Darrick J. Wong via Ocfs2-devel 2023-04-05 7:29 ` Amir Goldstein 2023-04-05 7:47 ` [f2fs-dev] " Christian Brauner 2023-04-05 7:47 ` Christian Brauner 2023-04-05 7:47 ` [Ocfs2-devel] " Christian Brauner via Ocfs2-devel 2023-04-06 5:02 ` Zorro Lang 2023-04-06 7:49 ` Christian Brauner 2023-04-04 17:14 ` [f2fs-dev] [PATCH 5/5] fstests/MAINTAINERS: add a co-maintainer for btrfs testing part Zorro Lang 2023-04-04 17:14 ` [Ocfs2-devel] " Zorro Lang via Ocfs2-devel 2023-04-04 17:14 ` Zorro Lang 2023-04-04 23:26 ` [f2fs-dev] " Darrick J. Wong 2023-04-04 23:26 ` Darrick J. Wong 2023-04-04 23:26 ` [Ocfs2-devel] " Darrick J. Wong via Ocfs2-devel 2023-04-06 14:17 ` [f2fs-dev] " David Sterba 2023-04-06 14:17 ` David Sterba 2023-04-06 14:17 ` [Ocfs2-devel] " David Sterba via Ocfs2-devel
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=20230405140202.bdp3lzgross2cjbt@zlang-mailbox \ --to=zlang@redhat.com \ --cc=amir73il@gmail.com \ --cc=anand.jain@oracle.com \ --cc=brauner@kernel.org \ --cc=ceph-devel@vger.kernel.org \ --cc=djwong@kernel.org \ --cc=ebiggers@kernel.org \ --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=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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.