linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Nick Piggin <npiggin@suse.de>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	Sachin Sant <sachinp@in.ibm.com>,
	linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Christoph Lameter <cl@linux-foundation.org>
Subject: Re: Next April 28: boot failure on PowerPC with SLQB
Date: Fri, 1 May 2009 00:00:33 +1000	[thread overview]
Message-ID: <20090501000033.ecce9ed8.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090430130542.GF6900@wotan.suse.de>

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

Hi Nick,

On Thu, 30 Apr 2009 15:05:42 +0200 Nick Piggin <npiggin@suse.de> wrote:
>
> Hmm, this might do it. The following code now passes some stress testing
> in a userspace harness wheras before it did not (and was obviously wrong).

Indeed that allows it to boot fine.  Thanks.

Tested-by: Stephen Rothwell <sfr@canb.auug.org.au>

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-04-30 14:00 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28  6:53 linux-next: Tree for April 28 Stephen Rothwell
2009-04-28 11:10 ` Next April 28: boot failure on PowerPC with SLQB Sachin Sant
2009-04-28 11:22   ` Pekka Enberg
2009-04-29  7:04     ` Nick Piggin
2009-04-29 11:36     ` Nick Piggin
2009-04-29 16:26       ` Sachin Sant
2009-04-30  3:21         ` Stephen Rothwell
2009-04-30  4:11         ` Nick Piggin
2009-04-30  5:36           ` Sachin Sant
2009-04-30  6:03             ` Nick Piggin
2009-04-30  6:42               ` Sachin Sant
2009-04-30  6:41             ` Nick Piggin
2009-04-30  9:47               ` Sachin Sant
2009-04-30 10:35                 ` Nick Piggin
2009-04-30 10:38                   ` Pekka Enberg
2009-04-30 11:00                     ` Stephen Rothwell
2009-04-30 11:10                       ` Pekka Enberg
2009-04-30 11:18                       ` Nick Piggin
2009-04-30 11:20                         ` Pekka Enberg
2009-04-30 11:26                           ` Nick Piggin
2009-04-30 13:05                           ` Nick Piggin
2009-04-30 14:00                             ` Stephen Rothwell [this message]
2009-04-30 14:10                               ` Nick Piggin
2009-05-03 11:51                                 ` Pekka Enberg
2009-04-30 14:10                             ` Anton Vorontsov
2009-05-03 11:51                               ` Pekka Enberg
2009-04-28 15:22 ` [PATCH] lockd: fix FILE_LOCKING=n build error Randy Dunlap
2009-04-28 15:38   ` Felix Blyakher
2009-04-28 17:21   ` J. Bruce Fields
2009-04-28 17:51     ` Randy Dunlap
2009-04-28 18:15       ` Trond Myklebust
2009-04-28 21:01         ` [PATCH v2] " Randy Dunlap
2009-04-28 21:40           ` 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=20090501000033.ecce9ed8.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=npiggin@suse.de \
    --cc=penberg@cs.helsinki.fi \
    --cc=sachinp@in.ibm.com \
    /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).