[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080723154533.GA12595@fieldses.org>
Date: Wed, 23 Jul 2008 11:45:33 -0400
From: "J. Bruce Fields" <bfields@...ldses.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Harvey Harrison <harvey.harrison@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Al Viro <viro@...IV.linux.org.uk>
Subject: Re: [PATCH] lockd: trivial sparse endian annotations
On Sun, Jul 20, 2008 at 11:42:11PM -0700, Andrew Morton wrote:
> On Thu, 17 Jul 2008 17:41:35 -0700 Harvey Harrison <harvey.harrison@...il.com> wrote:
>
> > fs/lockd/svcproc.c:115:11: warning: incorrect type in initializer (different base types)
> > fs/lockd/svcproc.c:115:11: expected int [signed] rc
> > fs/lockd/svcproc.c:115:11: got restricted __be32 [usertype] <noident>
> > ... and so on...
>
> Bruce handles lockd stuff.
Actually Trond normally handles client-specific lockd code (e.g.
fs/lockd/clnt*.c), though of course I'm happy to triage stuff and pass
it along.
> Not that a reader of ./MAINTAINERS would know this </hint>.
Would this help?
--b.
commit e8b43555a2a8c71e8501924e260f62b9545c598b
Author: J. Bruce Fields <bfields@...i.umich.edu>
Date: Wed Jul 23 08:49:50 2008 -0400
MAINTAINERS: mention lockd and sunrpc in nfs entries
The actual division of labor is a little vague in some of the common
code, but if the patches get to one of us then we can sort it out.
Signed-off-by: J. Bruce Fields <bfields@...i.umich.edu>
diff --git a/MAINTAINERS b/MAINTAINERS
index 0652ab3..c382ad3 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2418,7 +2418,7 @@ L: kernel-janitors@...r.kernel.org
W: http://www.kerneljanitors.org/
S: Maintained
-KERNEL NFSD
+KERNEL NFSD, SUNRPC, AND LOCKD SERVERS
P: J. Bruce Fields
M: bfields@...ldses.org
P: Neil Brown
@@ -3036,7 +3036,7 @@ M: ja@....bg
L: netdev@...r.kernel.org
S: Maintained
-NFS CLIENT
+NFS, SUNRPC, AND LOCKD CLIENTS
P: Trond Myklebust
M: Trond.Myklebust@...app.com
L: linux-nfs@...r.kernel.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists