Linux NFS development
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 06/11] NFSD: Remove NFSv4 dependency on NFSv3
Date: Fri, 8 Feb 2008 21:20:33 +0100	[thread overview]
Message-ID: <20080208202033.GD31984@uranus.ravnborg.org> (raw)
In-Reply-To: <20080208175208.16261.74626.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>

On Fri, Feb 08, 2008 at 12:52:08PM -0500, Chuck Lever wrote:
> Clean up: Because NFSD_V4 "depends on" NFSD_V3, it appears as a child of
> the NFSD_V3 menu entry, and is not visible if NFSD_V3 is unselected.
> 
> Replace the dependency on NFSD_V3 with a "select NFSD_V3".  This makes
> NFSD_V4 look and work just like NFS_V3, while ensuring that NFSD_V3 is
> enabled if NFSD_V4 is.
> 
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> 
>  fs/Kconfig |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/Kconfig b/fs/Kconfig
> index 9ad62a9..4c16789 100644
> --- a/fs/Kconfig
> +++ b/fs/Kconfig
> @@ -1723,7 +1723,8 @@ config NFSD_V3_ACL
>  
>  config NFSD_V4
>  	bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
> -	depends on NFSD && NFSD_V3 && EXPERIMENTAL
> +	depends on NFSD && EXPERIMENTAL
> +	select NFSD_V3
>  	select RPCSEC_GSS_KRB5
>  	help
>  	  This option enables support in your system's NFS server for

This use of select is questionable. In general it is bad to select
a symbol with dependencies.
In this case the dependencies of NFSD_V3 are duplicated for NFSD_V4
so we will not se erratic configurations but do you remember to
update NFSD_V4 when you add a depends on NFSD_V3?

But I see no other clean way to do it rithg now.

	Sam

  parent reply	other threads:[~2008-02-08 20:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 17:52 [PATCH 06/11] NFSD: Remove NFSv4 dependency on NFSv3 Chuck Lever
     [not found] ` <20080208175208.16261.74626.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-02-08 20:20   ` Sam Ravnborg [this message]
     [not found]     ` <20080208202033.GD31984-QabhHTsIXMSnlFQ6Q1D1Y0B+6BGkLq7r@public.gmane.org>
2008-02-08 21:08       ` Chuck Lever
2008-02-08 21:50         ` Sam Ravnborg

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=20080208202033.GD31984@uranus.ravnborg.org \
    --to=sam-uyr5n9q2vtjg9huczpvpmw@public.gmane.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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