From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>, NeilBrown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: [-mm patch] fs/nfsd/nfs4state.c: make a struct static
Date: Tue, 4 Apr 2006 18:30:10 +0200 [thread overview]
Message-ID: <20060404163010.GQ6529@stusta.de> (raw)
In-Reply-To: <20060404014504.564bf45a.akpm@osdl.org>
On Tue, Apr 04, 2006 at 01:45:04AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.16-mm2:
>...
> +knfsd-locks-flag-nfsv4-owned-locks.patch
>...
> knfsd updates.
>...
This patch makes the needlessly global struct nfsd_posix_mng_ops static.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.17-rc1-mm1-full/fs/nfsd/nfs4state.c.old 2006-04-04 18:03:25.000000000 +0200
+++ linux-2.6.17-rc1-mm1-full/fs/nfsd/nfs4state.c 2006-04-04 18:03:38.000000000 +0200
@@ -2507,7 +2507,7 @@
/* Hack!: For now, we're defining this just so we can use a pointer to it
* as a unique cookie to identify our (NFSv4's) posix locks. */
-struct lock_manager_operations nfsd_posix_mng_ops = {
+static struct lock_manager_operations nfsd_posix_mng_ops = {
};
static inline void
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next parent reply other threads:[~2006-04-04 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060404014504.564bf45a.akpm@osdl.org>
2006-04-04 16:30 ` Adrian Bunk [this message]
2006-04-04 16:50 ` [NFS] [-mm patch] fs/nfsd/nfs4state.c: make a struct static J. Bruce Fields
2006-04-04 17:29 ` Adrian Bunk
2006-04-05 2:27 ` 2.6.17-rc1-mm1, nfsd/reiser4 BUG Zan Lynx
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=20060404163010.GQ6529@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
/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