diff options
author | Herbert Xu <herbert@gondor.apana.org.au> | 2006-06-26 03:25:39 -0400 |
---|---|---|
committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-06-26 12:58:23 -0400 |
commit | f05e15b59467d97c30fbffed80db9e00b73d640b (patch) | |
tree | 90bc3b3a0854e0b063d438c8b151f0085d287ba0 /fs/Kconfig | |
parent | 5024ad4af69b3570e18d312786dc46318a1bad1a (diff) |
[PATCH] nfsd kconfig: select things at the closest tristate instead of bool
I noticed recently that my CONFIG_CRYPTO_MD5 turned into a y again instead
of m. It turns out that CONFIG_NFSD_V4 is selecting it to be y even though
I've chosen to compile nfsd as a module.
In general when we have a bool sitting under a tristate it is better to
select things you need from the tristate rather than the bool since that
allows the things you select to be modules.
The following patch does it for nfsd.
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Neil Brown <neilb@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'fs/Kconfig')
-rw-r--r-- | fs/Kconfig | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/fs/Kconfig b/fs/Kconfig index 1cdc043922d5..6c5051802bd2 100644 --- a/fs/Kconfig +++ b/fs/Kconfig | |||
@@ -1490,7 +1490,12 @@ config NFSD | |||
1490 | select LOCKD | 1490 | select LOCKD |
1491 | select SUNRPC | 1491 | select SUNRPC |
1492 | select EXPORTFS | 1492 | select EXPORTFS |
1493 | select NFS_ACL_SUPPORT if NFSD_V3_ACL || NFSD_V2_ACL | 1493 | select NFSD_V2_ACL if NFSD_V3_ACL |
1494 | select NFS_ACL_SUPPORT if NFSD_V2_ACL | ||
1495 | select NFSD_TCP if NFSD_V4 | ||
1496 | select CRYPTO_MD5 if NFSD_V4 | ||
1497 | select CRYPTO if NFSD_V4 | ||
1498 | select FS_POSIX_ACL if NFSD_V4 | ||
1494 | help | 1499 | help |
1495 | If you want your Linux box to act as an NFS *server*, so that other | 1500 | If you want your Linux box to act as an NFS *server*, so that other |
1496 | computers on your local network which support NFS can access certain | 1501 | computers on your local network which support NFS can access certain |
@@ -1528,7 +1533,6 @@ config NFSD_V3 | |||
1528 | config NFSD_V3_ACL | 1533 | config NFSD_V3_ACL |
1529 | bool "Provide server support for the NFSv3 ACL protocol extension" | 1534 | bool "Provide server support for the NFSv3 ACL protocol extension" |
1530 | depends on NFSD_V3 | 1535 | depends on NFSD_V3 |
1531 | select NFSD_V2_ACL | ||
1532 | help | 1536 | help |
1533 | Implement the NFSv3 ACL protocol extension for manipulating POSIX | 1537 | Implement the NFSv3 ACL protocol extension for manipulating POSIX |
1534 | Access Control Lists on exported file systems. NFS clients should | 1538 | Access Control Lists on exported file systems. NFS clients should |
@@ -1538,10 +1542,6 @@ config NFSD_V3_ACL | |||
1538 | config NFSD_V4 | 1542 | config NFSD_V4 |
1539 | bool "Provide NFSv4 server support (EXPERIMENTAL)" | 1543 | bool "Provide NFSv4 server support (EXPERIMENTAL)" |
1540 | depends on NFSD_V3 && EXPERIMENTAL | 1544 | depends on NFSD_V3 && EXPERIMENTAL |
1541 | select NFSD_TCP | ||
1542 | select CRYPTO_MD5 | ||
1543 | select CRYPTO | ||
1544 | select FS_POSIX_ACL | ||
1545 | help | 1545 | help |
1546 | If you would like to include the NFSv4 server as well as the NFSv2 | 1546 | If you would like to include the NFSv4 server as well as the NFSv2 |
1547 | and NFSv3 servers, say Y here. This feature is experimental, and | 1547 | and NFSv3 servers, say Y here. This feature is experimental, and |