* next: build fails at fs/lockd/svclock.c @ 2009-05-04 13:23 Alexander Beregalov 2009-05-04 13:39 ` Trond Myklebust 0 siblings, 1 reply; 3+ messages in thread From: Alexander Beregalov @ 2009-05-04 13:23 UTC (permalink / raw) To: linux-next, Felix Blyakher, J. Bruce Fields, linux-nfs Hi Randconfig fails like this fs/lockd/svclock.c: In function 'nlmsvc_freegrantargs': fs/lockd/svclock.c:330: error: implicit declaration of function 'locks_release_private' caused by a9e61e25f9d2 (lockd: call locks_release_private to cleanup per-filesystem state) # CONFIG_FILE_LOCKING is not set CONFIG_LOCKD=y ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: next: build fails at fs/lockd/svclock.c 2009-05-04 13:23 next: build fails at fs/lockd/svclock.c Alexander Beregalov @ 2009-05-04 13:39 ` Trond Myklebust [not found] ` <1241444370.5754.5.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org> 0 siblings, 1 reply; 3+ messages in thread From: Trond Myklebust @ 2009-05-04 13:39 UTC (permalink / raw) To: Alexander Beregalov Cc: linux-next, Felix Blyakher, J. Bruce Fields, linux-nfs On Mon, 2009-05-04 at 17:23 +0400, Alexander Beregalov wrote: > Hi > > Randconfig fails like this > > fs/lockd/svclock.c: In function 'nlmsvc_freegrantargs': > fs/lockd/svclock.c:330: error: implicit declaration of function > 'locks_release_private' > > caused by a9e61e25f9d2 > (lockd: call locks_release_private to cleanup per-filesystem state) > > > # CONFIG_FILE_LOCKING is not set > CONFIG_LOCKD=y > -- See the posting "[PATCH v2] lockd: fix FILE_LOCKING=n build error" by Randy Dunlap last Tuesday. Trond ^ permalink raw reply [flat|nested] 3+ messages in thread
[parent not found: <1241444370.5754.5.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>]
* Re: next: build fails at fs/lockd/svclock.c [not found] ` <1241444370.5754.5.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org> @ 2009-05-11 18:46 ` J. Bruce Fields 0 siblings, 0 replies; 3+ messages in thread From: J. Bruce Fields @ 2009-05-11 18:46 UTC (permalink / raw) To: Trond Myklebust Cc: Alexander Beregalov, linux-next, Felix Blyakher, linux-nfs On Mon, May 04, 2009 at 09:39:30AM -0400, Trond Myklebust wrote: > On Mon, 2009-05-04 at 17:23 +0400, Alexander Beregalov wrote: > > Hi > > > > Randconfig fails like this > > > > fs/lockd/svclock.c: In function 'nlmsvc_freegrantargs': > > fs/lockd/svclock.c:330: error: implicit declaration of function > > 'locks_release_private' > > > > caused by a9e61e25f9d2 > > (lockd: call locks_release_private to cleanup per-filesystem state) > > > > > > # CONFIG_FILE_LOCKING is not set > > CONFIG_LOCKD=y > > -- > > See the posting "[PATCH v2] lockd: fix FILE_LOCKING=n build error" by > Randy Dunlap last Tuesday. What happened to this--is it in some maintainer's tree now? --b. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-05-11 18:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-05-04 13:23 next: build fails at fs/lockd/svclock.c Alexander Beregalov
2009-05-04 13:39 ` Trond Myklebust
[not found] ` <1241444370.5754.5.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-11 18:46 ` J. Bruce Fields
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox