From: Benny Halevy <bhalevy@panasas•com>
To: Trond Myklebust <trond.myklebust@fys•uio.no>
Cc: Andy Adamson <andros@netapp•com>,
Stephen Rothwell <sfr@canb•auug.org.au>,
"J. Bruce Fields" <bfields@fieldses•org>,
linux-next@vger•kernel.org, pnfs@linux-nfs•org,
linux-nfs@vger•kernel.org, Benny Halevy <bhalevy@panasas•com>
Subject: [PATCH 1/3] SQUASHME: nfs41: always define nfs_client.cl_minorversion
Date: Mon, 6 Apr 2009 10:49:49 +0300 [thread overview]
Message-ID: <1239004189-8675-1-git-send-email-bhalevy@panasas.com> (raw)
In-Reply-To: <49D9B2B9.5010401@panasas.com>
We want to avoid using #ifdef when using it.
Reported-by: Stephen Rothwell <sfr@canb•auug.org.au>
Signed-off-by: Benny Halevy <bhalevy@panasas•com>
---
include/linux/nfs_fs_sb.h | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/include/linux/nfs_fs_sb.h b/include/linux/nfs_fs_sb.h
index 2ce5ada..0043bf5 100644
--- a/include/linux/nfs_fs_sb.h
+++ b/include/linux/nfs_fs_sb.h
@@ -38,7 +38,7 @@ struct nfs_client {
struct rpc_clnt * cl_rpcclient;
const struct nfs_rpc_ops *rpc_ops; /* NFS protocol vector */
int cl_proto; /* Network transport protocol */
-
+ u32 cl_minorversion;/* NFSv4 minorversion */
struct rpc_cred *cl_machine_cred;
#ifdef CONFIG_NFS_V4
@@ -70,7 +70,6 @@ struct nfs_client {
*/
char cl_ipaddr[48];
unsigned char cl_id_uniquifier;
- u32 cl_minorversion;
int (* cl_call_sync)(struct nfs_server *server,
struct rpc_message *msg,
struct nfs4_sequence_args *args,
--
1.6.2.1
next prev parent reply other threads:[~2009-04-06 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 6:29 linux-next: nfs tree build failures Stephen Rothwell
2009-04-06 7:43 ` Benny Halevy
2009-04-06 7:49 ` Benny Halevy [this message]
[not found] ` <49D9B2B9.5010401-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2009-04-06 7:49 ` [PATCH 2/3] SQUASHME: nfs41: move nfs4_session_set_rwsize into CONFIG_NFS_V4 Benny Halevy
2009-04-06 7:50 ` [PATCH 3/3] SQUASHME: inline nfs4_restart_rpc Benny Halevy
2009-04-06 23:34 ` linux-next: nfs tree build failures Trond Myklebust
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=1239004189-8675-1-git-send-email-bhalevy@panasas.com \
--to=bhalevy@panasas$(echo .)com \
--cc=andros@netapp$(echo .)com \
--cc=bfields@fieldses$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-nfs@vger$(echo .)kernel.org \
--cc=pnfs@linux-nfs$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=trond.myklebust@fys$(echo .)uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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