lockd: fix FILE_LOCKING=n build error
authorRandy Dunlap <randy.dunlap@oracle.com>
Tue, 12 May 2009 20:28:09 +0000 (13:28 -0700)
committerJ. Bruce Fields <bfields@citi.umich.edu>
Wed, 13 May 2009 19:59:10 +0000 (15:59 -0400)
commitdd4dc82d4c129babca9b48b219cff0add5ff4132
treed5dc1a1aa59796d197564451fb49fa6c13e5968c
parent02cb2858dbfe216bd4a91c4afb4e259ef3b9e151
lockd: fix FILE_LOCKING=n build error

lockd/svclock.c is missing a header file <linux/fs.h>.

<linux/fs.h> is missing a definition of locks_release_private()
for the config case of FILE_LOCKING=n, causing a build error:

fs/lockd/svclock.c:330: error: implicit declaration of function 'locks_release_private'

lockd without FILE_LOCKING doesn't make sense, so make LOCKD and LOCKD_V4
depend on FILE_LOCKING, and make NFS depend on FILE_LOCKING.

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
fs/Kconfig
fs/nfs/Kconfig