From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: linux-next: Tree for Nov 8 (various vfs)
Date: Fri, 08 Nov 2013 10:48:53 -0800 [thread overview]
Message-ID: <527D3215.5020909@infradead.org> (raw)
In-Reply-To: <20131108194753.c45ecb7db2fdd59e156d8acd@canb.auug.org.au>
On 11/08/13 00:47, Stephen Rothwell wrote:
> Hi all,
>
> Please do *not* add any v3.14 material to linux-next until after
> v3.13-rc1 is released.
>
> [A bit of a mess today :-(]
>
> Changes since 20131107:
>
> The vfs tree lost its build failure but gained a conflict against Linus'
> tree.
>
> The userns tree gained conflicts against the vfs tree and a build failure
> caused by merge issues, so I dropped it for today.
>
> The akpm-current tree gained conflicts against the vfs and tip trees.
on both i386 and x86_64:
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]
--
~Randy
next prev parent reply other threads:[~2013-11-08 18:48 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 ` Randy Dunlap [this message]
2013-11-08 19:35 ` linux-next: Tree for Nov 8 (various vfs) Al Viro
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=527D3215.5020909@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
/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).