linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: linux-next <linux-next@vger.kernel.org>,
	Felix Blyakher <felixb@sgi.com>,
	"J. Bruce Fields" <bfields@citi.umich.edu>,
	linux-nfs@vger.kernel.org
Subject: Re: next: build fails at fs/lockd/svclock.c
Date: Mon, 04 May 2009 09:39:30 -0400	[thread overview]
Message-ID: <1241444370.5754.5.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <a4423d670905040623q48eb552ft3bd107d6aa71d63b@mail.gmail.com>

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

  reply	other threads:[~2009-05-04 13:39 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 [this message]
     [not found]   ` <1241444370.5754.5.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-11 18:46     ` J. Bruce Fields

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=1241444370.5754.5.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=a.beregalov@gmail.com \
    --cc=bfields@citi.umich.edu \
    --cc=felixb@sgi.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.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).