From: "J. Bruce Fields" <bfields@fieldses.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
matthew@wil.cx
Subject: Re: nfsd changes for 3.6
Date: Tue, 31 Jul 2012 10:36:00 -0400 [thread overview]
Message-ID: <20120731143600.GD27834@fieldses.org> (raw)
In-Reply-To: <20120731142948.GC27834@fieldses.org>
On Tue, Jul 31, 2012 at 10:29:48AM -0400, bfields wrote:
> Please pull nfsd (and some lockd and a couple locks/lease) changes from:
By the way, for a few years now I've been semi-regularly picking up
locks.c changes for my tree. I wonder if I should be.
At the least we should probably remove this entry from MAINTAINERS? And
by default I suppose that stuff reverts to Al, who rumor has it will
have a fair number of locks.c patches next time around.
Or I'm happy to claim to be maintainer of that file if somebody prefers,
it doesn't matter much to me.
--b.
diff --git a/MAINTAINERS b/MAINTAINERS
index 3e30a3a..305ac2c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2767,15 +2767,6 @@ F: include/scsi/fc/
F: include/scsi/libfc.h
F: include/scsi/libfcoe.h
-FILE LOCKING (flock() and fcntl()/lockf())
-M: Matthew Wilcox <matthew@wil.cx>
-L: linux-fsdevel@vger.kernel.org
-S: Maintained
-F: include/linux/fcntl.h
-F: include/linux/fs.h
-F: fs/fcntl.c
-F: fs/locks.c
-
FILESYSTEMS (VFS and infrastructure)
M: Alexander Viro <viro@zeniv.linux.org.uk>
L: linux-fsdevel@vger.kernel.org
next prev parent reply other threads:[~2012-07-31 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 14:29 nfsd changes for 3.6 J. Bruce Fields
2012-07-31 14:29 ` J. Bruce Fields
2012-07-31 14:36 ` J. Bruce Fields [this message]
2012-07-31 21:54 ` Linus Torvalds
2012-07-31 21:54 ` Linus Torvalds
2012-08-01 11:56 ` [PATCH] locks: remove unused lm_release_private J. Bruce Fields
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=20120731143600.GD27834@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=torvalds@linux-foundation.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 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.