From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jens Axboe <jens.axboe@oracle•com>
Cc: James Bottomley <James.Bottomley@HansenPartnership•com>,
Sachin Sant <sachinp@in•ibm.com>,
linuxppc-dev@ozlabs•org, linux-next@vger•kernel.org,
linux-scsi <linux-scsi@vger•kernel.org>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>
Subject: Re: Next March 25: Boot failure on powerpc [recursive locking detected]
Date: Fri, 27 Mar 2009 17:53:01 +1100 [thread overview]
Message-ID: <20090327175301.c4c2dfe3.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090327064208.GQ27476@kernel.dk>
[-- Attachment #1: Type: text/plain, Size: 353 bytes --]
Hi Jens,
On Fri, 27 Mar 2009 07:42:08 +0100 Jens Axboe <jens.axboe@oracle•com> wrote:
>
> I'll update for-next, sorry about that. I had dropped it from
> for-2.6.30, but forgot to update akpm/next branches.
Thanks. Its OK for today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-03-27 6:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 8:12 linux-next: Tree for March 25 Stephen Rothwell
2009-03-25 11:34 ` Next March 25: net/netfilter/xt_LED build failure Sachin Sant
2009-03-25 11:43 ` Next March 25: staging/epl build break Sachin Sant
2009-03-25 16:04 ` Randy Dunlap
2009-03-25 11:52 ` Next March 25 : arch/x86/kernel : k8_northbridges Sachin Sant
2009-03-25 14:13 ` Next March 25: Boot failure on powerpc [recursive locking detected] Sachin Sant
2009-03-26 6:34 ` Sachin Sant
2009-03-26 13:50 ` James Bottomley
2009-03-27 5:56 ` Stephen Rothwell
2009-03-27 6:42 ` Jens Axboe
2009-03-27 6:53 ` Stephen Rothwell [this message]
2009-03-25 16:06 ` linux-next: Tree for March 25 (drivers/media/video/cx231xx) Randy Dunlap
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=20090327175301.c4c2dfe3.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=James.Bottomley@HansenPartnership$(echo .)com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=jens.axboe@oracle$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-scsi@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=sachinp@in$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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