linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	neilb@suse.de, linux-next@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for August 13 (nfsd)
Date: Thu, 14 Aug 2008 18:47:52 -0400	[thread overview]
Message-ID: <20080814224752.GR23859@fieldses.org> (raw)
In-Reply-To: <20080814111633.55f5f1e8@surf>

On Thu, Aug 14, 2008 at 11:16:33AM +0200, Thomas Petazzoni wrote:
> Le Wed, 13 Aug 2008 14:09:31 -0400,
> "J. Bruce Fields" <bfields@fieldses.org> a écrit :
> 
> > Looks like that's just two more functions that need to be stubbed out
> > in the case where CONFIG_FILE_LOCKING is undefined?--hopefully Thomas
> > Petazzoni (cc'd) could be talked into reproducing this and sending me
> > an incremental fix....
> 
> Here is an incremental fix.

Thanks, I've updated the version in

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

--b.


> 
> ---
> 
> Fixup configure out fs locks support
> 
> This patch adds a few more stubs required to get NFS server to compile
> properly with CONFIG_FILE_LOCKING=n.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> 
> ---
>  include/linux/fs.h |    2 ++
>  1 file changed, 2 insertions(+)
> 
> Index: linuxdev/include/linux/fs.h
> ===================================================================
> --- linuxdev.orig/include/linux/fs.h
> +++ linuxdev/include/linux/fs.h
> @@ -1050,6 +1050,8 @@
>  #define __break_lease(a, b) ({ 0; })
>  #define lease_get_mtime(a, b) ({ })
>  #define generic_setlease(a, b, c) ({ -EINVAL; })
> +#define vfs_setlease(a, b, c) ({ -EINVAL; })
> +#define lease_modify(a, b) ({ -EINVAL; })
>  #define lock_may_read(a, b, c) ({ 1; })
>  #define lock_may_write(a, b, c) ({ 1; })
>  #endif /* !CONFIG_FILE_LOCKING */
> 
> 
> -- 
> Thomas Petazzoni, Free Electrons
> Kernel, drivers and embedded Linux development,
> consulting, training and support.
> http://free-electrons.com

  parent reply	other threads:[~2008-08-14 22:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13  7:24 linux-next: Tree for August 13 Stephen Rothwell
2008-08-13 11:05 ` Takashi Iwai
2008-08-13 11:42   ` Stephen Rothwell
2008-08-13 13:08   ` Alan Cox
2008-08-13 13:37     ` Takashi Iwai
2008-08-13 14:40       ` Takashi Iwai
2008-08-14  9:57         ` Takashi Iwai
2008-08-13 17:47 ` linux-next: Tree for August 13 (nfsd) Randy Dunlap
2008-08-13 18:09   ` J. Bruce Fields
2008-08-14  9:16     ` Thomas Petazzoni
2008-08-14 16:44       ` Randy Dunlap
2008-08-14 22:47       ` J. Bruce Fields [this message]
2008-08-18 11:01       ` Thomas Petazzoni

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=20080814224752.GR23859@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    --cc=thomas.petazzoni@free-electrons.com \
    /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;
as well as URLs for NNTP newsgroup(s).