public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Zorro Lang <zlang@redhat.com>
Cc: Zorro Lang <zlang@kernel.org>,
	fstests@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 4/5] fstests/MAINTAINERS: add some specific reviewers
Date: Thu, 6 Apr 2023 09:49:40 +0200	[thread overview]
Message-ID: <20230406-amputation-eiern-a55f52bbf32c@brauner> (raw)
In-Reply-To: <20230406050228.5ujhuamrqqdjqu77@zlang-mailbox>

On Thu, Apr 06, 2023 at 01:02:28PM +0800, Zorro Lang wrote:
> On Wed, Apr 05, 2023 at 09:47:55AM +0200, Christian Brauner wrote:
> > On Wed, Apr 05, 2023 at 01:14:10AM +0800, Zorro Lang wrote:
> > > Some people contribute to someone specific fs testing mostly, record
> > > some of them as Reviewer.
> > > 
> > > Signed-off-by: Zorro Lang <zlang@kernel.org>
> > > ---
> > > 
> > > If someone doesn't want to be in cc list of related fstests patch, please
> > > reply this email, I'll remove that reviewer line.
> > > 
> > > Or if someone else (who contribute to fstests very much) would like to a
> > > specific reviewer, nominate yourself to get a review.
> > > 
> > > Thanks,
> > > Zorro
> > > 
> > >  MAINTAINERS | 6 ++++++
> > >  1 file changed, 6 insertions(+)
> > > 
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 620368cb..0ad12a38 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -108,6 +108,7 @@ Maintainers List
> > >  	  or reviewer or co-maintainer can be in cc list.
> > >  
> > >  BTRFS
> > > +R:	Filipe Manana <fdmanana@suse.com>
> > >  L:	linux-btrfs@vger.kernel.org
> > >  S:	Supported
> > >  F:	tests/btrfs/
> > > @@ -137,16 +138,19 @@ F:	tests/f2fs/
> > >  F:	common/f2fs
> > >  
> > >  FSVERITY
> > > +R:	Eric Biggers <ebiggers@google.com>
> > >  L:	fsverity@lists.linux.dev
> > >  S:	Supported
> > >  F:	common/verity
> > >  
> > >  FSCRYPT
> > > +R:	Eric Biggers <ebiggers@google.com>
> > >  L:      linux-fscrypt@vger.kernel.org
> > >  S:	Supported
> > >  F:	common/encrypt
> > >  
> > >  FS-IDMAPPED
> > 
> > I'd just make this VFS since src/vfs/ covers generic vfs functionality.
> > 
> > But up to you,
> 
> Sure, it can be "VFS". I didn't use "VFS" directly due to vfs is larger, current
> src/vfs only tests a small part of it, more tests are under tests/generic directory.
> And we don't have many vfs tests, e.g. we don't test new mount API in fstests.
> 
> We need a way to sort out "VFS" only files/tests (e.g. group tag), and if we use
> "VFS" at here, would you like to be a reviewer of all vfs tests?

Sure, I can try and help.

  reply	other threads:[~2023-04-06  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
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 [this message]
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=20230406-amputation-eiern-a55f52bbf32c@brauner \
    --to=brauner@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=zlang@kernel.org \
    --cc=zlang@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