From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 18
Date: Tue, 19 Aug 2014 08:24:26 -0700 [thread overview]
Message-ID: <20140819152426.GA19665@roeck-us.net> (raw)
In-Reply-To: <20140818133259.3d1182fd@canb.auug.org.au>
On Mon, Aug 18, 2014 at 01:32:59PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add code intended for v3.18 until after v3.17-rc1 is
> released.
>
> Changes since 20140815:
>
> The sound-asoc tree gained a build failure for which I reverted a commit.
>
> The regulator tree gained a build failure so I used the verison from
> next-20140815.
>
> The staging tree gained a build failure for which I applied a fix patch.
>
> Non-merge commits (relative to Linus' tree): 1010
> 955 files changed, 25072 insertions(+), 21100 deletions(-)
>
Something in this tree appears to be completely broken. All my qemu tests
fail with it. It _seems_ that the problem is related to either mount related
or to locking related code. Someone might want to have a look. Given that
all of my runtime tests crash, it is probably easy to reproduce by just
trying to load an image on an x86 system.
Guenter
next prev parent reply other threads:[~2014-08-19 15:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 3:32 linux-next: Tree for Aug 18 Stephen Rothwell
2014-08-18 3:52 ` Stephen Rothwell
2014-08-19 15:24 ` Guenter Roeck [this message]
2014-08-19 18:42 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-08-18 4:02 Stephen Rothwell
2023-08-18 7:49 Stephen Rothwell
2022-08-18 4:29 Stephen Rothwell
2021-08-18 8:04 Stephen Rothwell
2020-08-18 4:55 Stephen Rothwell
2016-08-18 4:41 Stephen Rothwell
2015-08-18 11:40 Stephen Rothwell
2011-08-18 6:00 Stephen Rothwell
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=20140819152426.GA19665@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).