public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle•de>
To: Paul Mackerras <paulus@samba•org>, linuxppc-dev@ozlabs•org
Subject: Re: Don't pass the stack pointer to zImage's start() function
Date: Fri, 16 Mar 2007 19:37:48 +0100	[thread overview]
Message-ID: <20070316183748.GA30637@aepfle.de> (raw)
In-Reply-To: <20070315042904.GE14061@localhost.localdomain>

On Thu, Mar 15, David Gibson wrote:

> At present, the zImage entry code passes a copy of the stack pointer
> to the start() function.  There's no real reason for this; the only
> thing start() does with it is print it out.  It appears to be a
> leftover debugging hack, so, this patch removes it.
> 
> Signed-off-by: David Gibson <david@gibson•dropbear.id.au>

NACK.
It helps to determine the firmware memory layout.

  parent reply	other threads:[~2007-03-16 18:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15  4:29 Don't pass the stack pointer to zImage's start() function David Gibson
2007-03-15  4:35 ` Tony Breeds
2007-03-15  5:18   ` David Gibson
2007-03-16 18:37 ` Olaf Hering [this message]
2007-03-16 19:26   ` Josh Boyer
2007-03-16 20:04     ` Olaf Hering

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=20070316183748.GA30637@aepfle.de \
    --to=olaf@aepfle$(echo .)de \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=paulus@samba$(echo .)org \
    /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