All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 18
Date: Wed, 20 Aug 2014 04:42:44 +1000	[thread overview]
Message-ID: <20140820044244.7e58b9f3@canb.auug.org.au> (raw)
In-Reply-To: <20140819152426.GA19665@roeck-us.net>

[-- Attachment #1: Type: text/plain, Size: 618 bytes --]

Hi Guenter,

On Tue, 19 Aug 2014 08:24:26 -0700 Guenter Roeck <linux@roeck-us.net> wrote:
>
> 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.

Hopefully you are seeing what will be fixed by Hugh Dickins' patch in
today's linux-next.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-08-19 18:42 UTC|newest]

Thread overview: 13+ 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
2014-08-19 18:42   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-08-18 20:57 Mark Brown
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=20140820044244.7e58b9f3@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.