From: "J. Bruce Fields" <bfields@fieldses.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
neilb@suse.de, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Subject: Re: linux-next: Tree for August 13 (nfsd)
Date: Wed, 13 Aug 2008 14:09:31 -0400 [thread overview]
Message-ID: <20080813180931.GC26765@fieldses.org> (raw)
In-Reply-To: <20080813104748.13848196.randy.dunlap@oracle.com>
On Wed, Aug 13, 2008 at 10:47:48AM -0700, Randy Dunlap wrote:
> linux-next-20080813/fs/nfsd/nfs4state.c:259: error: implicit declaration of function 'vfs_setlease'
> linux-next-20080813/fs/nfsd/nfs4state.c:1386: error: implicit declaration of function 'lease_modify'
> make[3]: *** [fs/nfsd/nfs4state.o] Error 1
>
>
> config attached.
Probably relevant pieces:
# CONFIG_FILE_LOCKING is not set
...
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
CONFIG_NFSD_V4=y
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....
--b.
next prev parent reply other threads:[~2008-08-13 18:10 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 [this message]
2008-08-14 9:16 ` Thomas Petazzoni
2008-08-14 16:44 ` Randy Dunlap
2008-08-14 22:47 ` J. Bruce Fields
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=20080813180931.GC26765@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).