From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Don't pass the stack pointer to zImage's start() function
Date: Fri, 16 Mar 2007 14:26:57 -0500 [thread overview]
Message-ID: <1174073217.16140.10.camel@zod.rchland.ibm.com> (raw)
In-Reply-To: <20070316183748.GA30637@aepfle.de>
On Fri, 2007-03-16 at 19:37 +0100, Olaf Hering wrote:
> 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.
How, why is that useful, and where is that ever used?
josh
next prev parent reply other threads:[~2007-03-16 19:27 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
2007-03-16 19:26 ` Josh Boyer [this message]
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=1174073217.16140.10.camel@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=olaf@aepfle.de \
--cc=paulus@samba.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 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).