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. -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
