NFS: Use proper naming conventions for NFSv4.1 server scope fields
authorChuck Lever <chuck.lever@oracle.com>
Tue, 22 May 2012 02:44:31 +0000 (22:44 -0400)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Tue, 22 May 2012 20:45:43 +0000 (16:45 -0400)
commit79d4e1f0d8910f0214a57832ca6d589640d572c0
treec32a4ff22864b554061b0ea6f81667f9f4ef14cf
parent722baafc9e638714a69aa66e9ed24ef961ff350c
NFS: Use proper naming conventions for NFSv4.1 server scope fields

Clean up:  When naming fields and data types, follow established
conventions to facilitate accurate grep/cscope searches.

Additionally, for consistency, move the scope field into the NFSv4-
specific part of the nfs_client, and free that memory in the logic
that shuts down NFSv4 nfs_clients.

Introduced by commit 99fe60d0 "nfs41: exchange_id operation", April
1 2009.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
fs/nfs/client.c
fs/nfs/nfs4_fs.h
fs/nfs/nfs4proc.c
include/linux/nfs_fs_sb.h
include/linux/nfs_xdr.h