linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J . Bruce Fields" <bfields@fieldses.org>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, Eric Biggers <ebiggers@google.com>,
	Jeff Layton <jlayton@poochiereds.net>,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] MAINTAINERS: associate linux/fs.h with VFS instead of file locking
Date: Wed, 26 Apr 2017 21:00:51 -0400	[thread overview]
Message-ID: <20170427010051.GA31780@fieldses.org> (raw)
In-Reply-To: <20170426235356.78723-1-ebiggers3@gmail.com>

On Wed, Apr 26, 2017 at 04:53:56PM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
> 
> include/linux/fs.h and include/uapi/linux/fs.h deal with much more than
> just file locking.  Move them to the "FILESYSTEMS (VFS and
> infrastructure)" section of the MAINTAINERS file so that the first
> suggestion from get_maintainer.pl isn't the file locking maintainers,
> which has caused some confusion.

So that's why I was getting all that mail.  Thanks!

--b.

> 
> Cc: Jeff Layton <jlayton@poochiereds.net>
> Cc: J. Bruce Fields <bfields@fieldses.org>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
>  MAINTAINERS | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 22b509fb1c5e..2ac97d8c1a21 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5074,9 +5074,7 @@ M:	"J. Bruce Fields" <bfields@fieldses.org>
>  L:	linux-fsdevel@vger.kernel.org
>  S:	Maintained
>  F:	include/linux/fcntl.h
> -F:	include/linux/fs.h
>  F:	include/uapi/linux/fcntl.h
> -F:	include/uapi/linux/fs.h
>  F:	fs/fcntl.c
>  F:	fs/locks.c
>  
> @@ -5085,6 +5083,8 @@ M:	Alexander Viro <viro@zeniv.linux.org.uk>
>  L:	linux-fsdevel@vger.kernel.org
>  S:	Maintained
>  F:	fs/*
> +F:	include/linux/fs.h
> +F:	include/uapi/linux/fs.h
>  
>  FINTEK F75375S HARDWARE MONITOR AND FAN CONTROLLER DRIVER
>  M:	Riku Voipio <riku.voipio@iki.fi>
> -- 
> 2.13.0.rc0.306.g87b477812d-goog

  reply	other threads:[~2017-04-27  1:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 23:53 [PATCH] MAINTAINERS: associate linux/fs.h with VFS instead of file locking Eric Biggers
2017-04-27  1:00 ` J . Bruce Fields [this message]
2017-05-02 13:57   ` Jeff Layton
2017-05-23  1:17     ` Eric Biggers
2017-09-18 15:12 ` Jeff Layton
2017-09-18 19:16   ` J . Bruce Fields
2017-09-18 19:31     ` Jeff Layton

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=20170427010051.GA31780@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=ebiggers3@gmail.com \
    --cc=ebiggers@google.com \
    --cc=jlayton@poochiereds.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).