Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Manish Katiyar <mkatiyar@gmail.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/1] nfs : Define NFS_FS only when FILE_LOCKING is enabled
Date: Fri, 30 Jan 2009 10:06:40 -0500	[thread overview]
Message-ID: <20090130150640.GA22347@fieldses.org> (raw)
In-Reply-To: <ea11fea30901292038h5810bde4lf83470332b6b72c9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Fri, Jan 30, 2009 at 10:08:11AM +0530, Manish Katiyar wrote:
> Hi Bruce,
> 
> I didn't see this one merged in your 2.6.30 tree. Was it missed (since
> I had sent it to wrong list by mistake). Please ignore if already
> merged.

It should be there at:

	git://linux-nfs.org/~bfields/linux.git for-2.6.30

--b.

> 
> 
> Below patch enables NFS_FS only when FILE_LOCKING is enabled.
> 
> Signed-off-by: Manish Katiyar <mkatiyar@gmail.com>
> ---
>  fs/nfs/Kconfig |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/fs/nfs/Kconfig b/fs/nfs/Kconfig
> index 36fe20d..e93151e 100644
> --- a/fs/nfs/Kconfig
> +++ b/fs/nfs/Kconfig
> @@ -1,6 +1,7 @@
>  config NFS_FS
>        tristate "NFS client support"
>        depends on INET
> +       depends on FILE_LOCKING
>        select LOCKD
>        select SUNRPC
>        select NFS_ACL_SUPPORT if NFS_V3_ACL
> --
> 1.5.4.3
> 
> 
> Thanks -
> Manish

  parent reply	other threads:[~2009-01-30 15:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ea11fea30901290722s5d9fe1b4y8f6142bcd137eb2@mail.gmail.com>
     [not found] ` <ea11fea30901290722s5d9fe1b4y8f6142bcd137eb2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-30  4:38   ` [PATCH 0/1] nfs : Define NFS_FS only when FILE_LOCKING is enabled Manish Katiyar
     [not found]     ` <ea11fea30901292038h5810bde4lf83470332b6b72c9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-30 15:06       ` J. Bruce Fields [this message]
2009-01-30 16:40         ` J. Bruce Fields

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=20090130150640.GA22347@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mkatiyar@gmail.com \
    --cc=trond.myklebust@fys.uio.no \
    /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