From patchwork Thu Feb 17 13:55:06 2011 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jan Beulich X-Patchwork-Id: 570311 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by demeter1.kernel.org (8.14.4/8.14.3) with ESMTP id p1HDr8GT027576 for ; Thu, 17 Feb 2011 13:54:17 GMT Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756482Ab1BQNyQ (ORCPT ); Thu, 17 Feb 2011 08:54:16 -0500 Received: from vpn.id2.novell.com ([195.33.99.129]:54529 "EHLO vpn.id2.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755912Ab1BQNyQ convert rfc822-to-8bit (ORCPT ); Thu, 17 Feb 2011 08:54:16 -0500 Received: from EMEA1-MTA by vpn.id2.novell.com with Novell_GroupWise; Thu, 17 Feb 2011 13:54:14 +0000 Message-Id: <4D5D36CA0200007800032664@vpn.id2.novell.com> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Thu, 17 Feb 2011 13:55:06 +0000 From: "Jan Beulich" To: Cc: , Subject: [PATCH] re-order and improve fs/nfs/Kconfig Mime-Version: 1.0 Content-Disposition: inline Sender: linux-kbuild-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kbuild@vger.kernel.org X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.6 (demeter1.kernel.org [140.211.167.41]); Thu, 17 Feb 2011 13:54:17 +0000 (UTC) --- 2.6.38-rc5/fs/nfs/Kconfig +++ 2.6.38-rc5-kconfig-nfs/fs/nfs/Kconfig @@ -64,6 +64,7 @@ config NFS_V4 bool "NFS client support for NFS version 4" depends on NFS_FS select SUNRPC_GSS + select DNS_RESOLVER if NFS_USE_KERNEL_DNS help This option enables support for version 4 of the NFS protocol (RFC 3530) in the kernel's NFS client. @@ -74,9 +75,39 @@ config NFS_V4 If unsure, say Y. +choice + prompt "NFS DNS resolver" + default NFS_USE_KERNEL_DNS + depends on NFS_V4 + help + The kernel now provides a method for translating a host name into an + IP address. Select the first option if you would rather use your + own DNS resolver script. + +config NFS_USE_LEGACY_DNS + bool "Use the legacy NFS DNS resolver" + help + +config NFS_USE_KERNEL_DNS + bool "Use the in-kernel DNS resolver" + select KEYS + +endchoice + +config NFS_USE_NEW_IDMAPPER + bool "Use the new idmapper upcall routine" + depends on NFS_V4 && KEYS + help + Say Y here if you want NFS to use the new idmapper upcall functions. + You will need /sbin/request-key (usually provided by the keyutils + package). For details, read + . + + If you are unsure, say N. + config NFS_V4_1 bool "NFS client support for NFSv4.1 (EXPERIMENTAL)" - depends on NFS_FS && NFS_V4 && EXPERIMENTAL + depends on NFS_V4 && EXPERIMENTAL select PNFS_FILE_LAYOUT help This option enables support for minor version 1 of the NFSv4 protocol @@ -104,31 +135,3 @@ config NFS_FSCACHE help Say Y here if you want NFS data to be cached locally on disc through the general filesystem cache manager - -config NFS_USE_LEGACY_DNS - bool "Use the legacy NFS DNS resolver" - depends on NFS_V4 - help - The kernel now provides a method for translating a host name into an - IP address. Select Y here if you would rather use your own DNS - resolver script. - - If unsure, say N - -config NFS_USE_KERNEL_DNS - bool - depends on NFS_V4 && !NFS_USE_LEGACY_DNS - select DNS_RESOLVER - select KEYS - default y - -config NFS_USE_NEW_IDMAPPER - bool "Use the new idmapper upcall routine" - depends on NFS_V4 && KEYS - help - Say Y here if you want NFS to use the new idmapper upcall functions. - You will need /sbin/request-key (usually provided by the keyutils - package). For details, read - . - - If you are unsure, say N.