All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Lynch <ntl@pobox.com>
To: "B. N. Poornima" <poornima@in.ibm.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	ppc64 dev list <linuxppc64-dev@ozlabs.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Martin J. Bligh" <mbligh@mbligh.org>,
	roland@topspin.com
Subject: Re: [PATCH] prom_find_machine_type typo breaks pSeries lpar boot
Date: Wed, 14 Nov 2007 13:37:33 -0600	[thread overview]
Message-ID: <20071114193733.GK26313@localdomain> (raw)
In-Reply-To: <473AE9BE.8070001@in.ibm.com>

Hi-

B. N. Poornima wrote:
> >On Fri, 2005-06-03 at 14:25 -0500, Nathan Lynch wrote:
> >  
> >>Typo in prom_find_machine_type from Ben's recent patch "ppc64: Fix
> >>result code handling in prom_init" prevents pSeries LPAR systems from
> >>booting.
> >>
>
> Hello,
> Same typo has creped in again from 2.6.17 kernel onwards and causing 
> open firmware exception in pSeries systems.

Looking at the current code, I don't see how this analysis could be
correct.

> The patch that is provided solves the problem.

Which patch?  Did you forget to include it?

It would be best if you sent your problem report and any patches to
linuxppc-dev@ozlabs.org.  linuxppc64-dev is dead.

Thanks.

  reply	other threads:[~2007-11-14 19:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-03 14:52 2.6.12-rc5-git8 regression on PPC64 Martin J. Bligh
2005-06-03 17:42 ` Roland Dreier
2005-06-03 18:27   ` Nathan Lynch
2005-06-03 19:07     ` Roland Dreier
2005-06-03 19:25       ` [PATCH] prom_find_machine_type typo breaks pSeries lpar boot Nathan Lynch
2005-06-03 22:58         ` Benjamin Herrenschmidt
2007-11-14 12:27           ` B. N. Poornima
2007-11-14 19:37             ` Nathan Lynch [this message]
2007-11-16 10:10               ` B. N. Poornima
2007-11-14 22:13             ` Benjamin Herrenschmidt
2005-06-03 22:56     ` 2.6.12-rc5-git8 regression on PPC64 Benjamin Herrenschmidt

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=20071114193733.GK26313@localdomain \
    --to=ntl@pobox.com \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=mbligh@mbligh.org \
    --cc=poornima@in.ibm.com \
    --cc=roland@topspin.com \
    --cc=torvalds@osdl.org \
    /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.