From: Christoph Hellwig <hch@infradead.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Christian Brauner <brauner@kernel.org>,
Jeff Layton <jlayton@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
Jeff Layton <jlayton@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: create an entry for exportfs
Date: Fri, 27 Oct 2023 00:30:57 -0700 [thread overview]
Message-ID: <ZTtnMYJdfdIMuZnj@infradead.org> (raw)
In-Reply-To: <CAOQ4uxh+hWrMrP5A=fGRMK7uTxFFPKvJRNu+=Sc3ygXA1PzxvQ@mail.gmail.com>
On Fri, Oct 27, 2023 at 09:35:29AM +0300, Amir Goldstein wrote:
> On Fri, Oct 27, 2023 at 9:08 AM Christoph Hellwig <hch@infradead.org> wrote:
> >
> > On Thu, Oct 26, 2023 at 11:55:53PM +0300, Amir Goldstein wrote:
> > > Split the exportfs entry from the nfsd entry and add myself as reviewer.
> >
> > I think exportfs is by now very much VFS code.
> >
>
> Yes, that's the idea of making it a vfs sub-entry in MAINTAINERS.
>
> Is that an ACK? or did you mean that something needs to change
> in the patch?
I as mostly thinking of dropping the diretory and the separate entry.
That would also go along with your patch of making it a bool.
But if you feel strongly about that we can add you as an extra reviewer
for it :)
prev parent reply other threads:[~2023-10-27 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 20:55 [PATCH] MAINTAINERS: create an entry for exportfs Amir Goldstein
2023-10-27 6:08 ` Christoph Hellwig
2023-10-27 6:35 ` Amir Goldstein
2023-10-27 7:30 ` Christoph Hellwig [this message]
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=ZTtnMYJdfdIMuZnj@infradead.org \
--to=hch@infradead.org \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@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