From: Paul Mackerras <paulus@samba.org>
To: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Cc: linuxppc <linuxppc-dev@ozlabs.org>,
Anton Blanchard <anton@samba.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.24-rc1 on PPC64: machine check exception
Date: Fri, 16 Nov 2007 10:46:10 +1100 [thread overview]
Message-ID: <18236.55874.204068.358524@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <473C7B16.3050700@linux.vnet.ibm.com>
Vaidyanathan Srinivasan writes:
> This patch fixed the problem. I am able to run and profile ebizzy on 128-way
> PPC64. However this fix is not included in 2.6.24-rc2 as well.
> I will watch for inclusion of this fix in 2.6.24.
It's upstream in Linus' tree now, so it will be in -rc3.
Paul.
prev parent reply other threads:[~2007-11-15 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 13:49 2.6.24-rc1 on PPC64: machine check exception Vaidyanathan Srinivasan
2007-11-05 15:40 ` Anton Blanchard
2007-11-05 18:09 ` Vaidyanathan Srinivasan
2007-11-15 17:00 ` Vaidyanathan Srinivasan
2007-11-15 23:46 ` Paul Mackerras [this message]
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=18236.55874.204068.358524@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=svaidy@linux.vnet.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).