From: Al Viro <viro@ZenIV.linux.org.uk>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: linux-next: Tree for Nov 8 (various vfs)
Date: Fri, 8 Nov 2013 19:35:52 +0000 [thread overview]
Message-ID: <20131108193552.GQ13318@ZenIV.linux.org.uk> (raw)
In-Reply-To: <527D3215.5020909@infradead.org>
On Fri, Nov 08, 2013 at 10:48:53AM -0800, Randy Dunlap wrote:
> vfs build errors:
>
> fs/open.c:486:3: error: implicit declaration of function 'break_deleg_wait' [-Werror=implicit-function-declaration]
> fs/namei.c:3726:3: error: implicit declaration of function 'break_deleg_wait' [-Werror=implicit-function-declaration]
> fs/utimes.c:110:3: error: implicit declaration of function 'break_deleg_wait' [-Werror=implicit-function-declaration]
... when FILE_LOCKING isn't set. Yes, break_deleg_wait() is not defined in
that case (and its call sites are unreachable). Fixed and pushed...
prev parent reply other threads:[~2013-11-08 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 8:47 linux-next: Tree for Nov 8 Stephen Rothwell
2013-11-08 18:48 ` linux-next: Tree for Nov 8 (various vfs) Randy Dunlap
2013-11-08 19:35 ` Al Viro [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=20131108193552.GQ13318@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).