linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Olaf Hering <olh@suse.de>
Cc: linuxppc-dev@lists.linuxppc.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] zlibc updates for bootloader
Date: Mon, 1 Dec 2003 12:30:21 -0700	[thread overview]
Message-ID: <20031201193020.GG1166@stop.crashing.org> (raw)
In-Reply-To: <20031130145421.GA30681@suse.de>


On Sun, Nov 30, 2003 at 03:54:21PM +0100, Olaf Hering wrote:

> This patch fixes the zlibc debugging code. A printf is required for
> PReP, maybe also for other configs.

I'd like to suggest a different approach if possible.  That is to make
arch/ppc/boot/ make use of lib/zlib_deflate/.  Sam, should it be
possible to do something like this, build-wise ?

--
Tom Rini
http://gate.crashing.org/~trini/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2003-12-01 19:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-30 14:54 [PATCH] zlibc updates for bootloader Olaf Hering
2003-12-01 19:30 ` Tom Rini [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=20031201193020.GG1166@stop.crashing.org \
    --to=trini@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=olh@suse.de \
    --cc=sam@ravnborg.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).