From: Geoff Levand <geoffrey.levand@am.sony.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [0/3] RFC: Cleanups and improvements to the zImage wrapper
Date: Fri, 16 Feb 2007 08:47:30 -0800 [thread overview]
Message-ID: <45D5E022.4020306@am.sony.com> (raw)
In-Reply-To: <20070216062458.GA23008@localhost.localdomain>
David Gibson wrote:
> Here is a set of three patches that make some substantial changes to
> the zImage wrapper's flow of control. These changes make things more
> flexible, in order to more easily handle a wider variety of
> platforms. They also make some things clearer than previously.
>
> I think these are fairly close to ready to merge, but they need more
> testing on various platforms. In particular, I'm not terribly whether
> my changes will work correctly on old powermac platforms booting from
> COFF.
Could I request some in-line documentation be added as we have in other
parts of the kernel to describe function arguments, etc.?
-Geoff
prev parent reply other threads:[~2007-02-16 16:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 6:24 [0/3] RFC: Cleanups and improvements to the zImage wrapper David Gibson
2007-02-16 6:27 ` [PATCH 2/3] zImage: Cleanup and improve prep_kernel() David Gibson
2007-02-18 1:22 ` Geoff Levand
2007-02-18 7:21 ` David Gibson
2007-02-16 6:27 ` [PATCH 1/3] zImage: Add more flexible gunzip convenience functions David Gibson
2007-02-16 6:27 ` [PATCH 3/3] zImage: Cleanup and improve zImage entry point David Gibson
2007-02-18 1:22 ` Geoff Levand
2007-02-18 7:23 ` David Gibson
2007-02-19 0:26 ` Paul Mackerras
2007-02-19 0:48 ` David Gibson
2007-02-19 15:14 ` Geoff Levand
2007-02-19 19:59 ` Benjamin Herrenschmidt
2007-02-19 19:57 ` Benjamin Herrenschmidt
2007-02-19 20:37 ` Geoff Levand
2007-02-19 20:50 ` Benjamin Herrenschmidt
2007-02-19 21:14 ` Geoff Levand
2007-02-16 16:47 ` Geoff Levand [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=45D5E022.4020306@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.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.