From: "J. Bruce Fields" <bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
To: Trond Myklebust
<trond.myklebust-41N18TsMXrtuMpJDpNschA@public.gmane.org>
Cc: Alexander Beregalov
<a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-next <linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Felix Blyakher <felixb-sJ/iWh9BUns@public.gmane.org>,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: next: build fails at fs/lockd/svclock.c
Date: Mon, 11 May 2009 14:46:00 -0400 [thread overview]
Message-ID: <20090511184600.GD793@fieldses.org> (raw)
In-Reply-To: <1241444370.5754.5.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
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-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-05-11 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=20090511184600.GD793@fieldses.org \
--to=bfields-uc3wqj2krung9huczpvpmw@public.gmane.org \
--cc=a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=felixb-sJ/iWh9BUns@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=trond.myklebust-41N18TsMXrtuMpJDpNschA@public.gmane.org \
/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).