* [PATCH 2] MAINTAINERS: NFSD should be responsible for fs/exportfs
@ 2022-10-31 14:01 Chuck Lever
2022-10-31 17:05 ` Jeff Layton
0 siblings, 1 reply; 2+ messages in thread
From: Chuck Lever @ 2022-10-31 14:01 UTC (permalink / raw)
To: linux-nfs, linux-fsdevel
We recently received a patch for fs/exportfs/expfs.c, but there
isn't a subsystem maintainer listed for fs/exportfs:
Christian Brauner <brauner@kernel.org> (commit_signer:2/2=100%,authored:1/2=50%,added_lines:3/6=50%,removed_lines:2/6=33%)
Al Viro <viro@zeniv.linux.org.uk> (commit_signer:1/2=50%,authored:1/2=50%,added_lines:3/6=50%,removed_lines:4/6=67%)
Miklos Szeredi <mszeredi@redhat.com> (commit_signer:1/2=50%)
Amir Goldstein <amir73il@gmail.com> (commit_signer:1/2=50%)
linux-kernel@vger.kernel.org (open list)
Neil says:
> Looking at recent commits, patches come in through multiple
> different trees.
> nfsd certainly has an interest in expfs.c. The only other user is
> name_to_handle/open_by_handle API.
> I see it as primarily nfsd functionality which is useful enough to
> be exported directly to user-space.
> (It was created by me when I was nfsd maintainer - does that
> count?)
Suggested-by: Neil Brown <neilb@suse.de>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
The patch description in v1 was truncated. Here's a refresh.
diff --git a/MAINTAINERS b/MAINTAINERS
index 379945f82a64..61fb45cfc825 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11129,6 +11129,7 @@ L: linux-nfs@vger.kernel.org
S: Supported
W: http://nfs.sourceforge.net/
T: git git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git
+F: fs/exportfs/
F: fs/lockd/
F: fs/nfs_common/
F: fs/nfsd/
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH 2] MAINTAINERS: NFSD should be responsible for fs/exportfs
2022-10-31 14:01 [PATCH 2] MAINTAINERS: NFSD should be responsible for fs/exportfs Chuck Lever
@ 2022-10-31 17:05 ` Jeff Layton
0 siblings, 0 replies; 2+ messages in thread
From: Jeff Layton @ 2022-10-31 17:05 UTC (permalink / raw)
To: Chuck Lever, linux-nfs, linux-fsdevel
On Mon, 2022-10-31 at 10:01 -0400, Chuck Lever wrote:
> We recently received a patch for fs/exportfs/expfs.c, but there
> isn't a subsystem maintainer listed for fs/exportfs:
>
> Christian Brauner <brauner@kernel.org> (commit_signer:2/2=100%,authored:1/2=50%,added_lines:3/6=50%,removed_lines:2/6=33%)
> Al Viro <viro@zeniv.linux.org.uk> (commit_signer:1/2=50%,authored:1/2=50%,added_lines:3/6=50%,removed_lines:4/6=67%)
> Miklos Szeredi <mszeredi@redhat.com> (commit_signer:1/2=50%)
> Amir Goldstein <amir73il@gmail.com> (commit_signer:1/2=50%)
> linux-kernel@vger.kernel.org (open list)
>
> Neil says:
> > Looking at recent commits, patches come in through multiple
> > different trees.
> > nfsd certainly has an interest in expfs.c. The only other user is
> > name_to_handle/open_by_handle API.
> > I see it as primarily nfsd functionality which is useful enough to
> > be exported directly to user-space.
> > (It was created by me when I was nfsd maintainer - does that
> > count?)
>
> Suggested-by: Neil Brown <neilb@suse.de>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> The patch description in v1 was truncated. Here's a refresh.
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 379945f82a64..61fb45cfc825 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11129,6 +11129,7 @@ L: linux-nfs@vger.kernel.org
> S: Supported
> W: http://nfs.sourceforge.net/
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git
> +F: fs/exportfs/
> F: fs/lockd/
> F: fs/nfs_common/
> F: fs/nfsd/
>
>
Acked-by: Jeff Layton <jlayton@kernel.org>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-10-31 17:05 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-10-31 14:01 [PATCH 2] MAINTAINERS: NFSD should be responsible for fs/exportfs Chuck Lever
2022-10-31 17:05 ` Jeff Layton
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).