public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Olaf Hering <olh@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
	Tom Rini <trini@kernel.crashing.org>,
	linux-kernel@vger.kernel.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] fix zlib debug in ppc boot header
Date: Wed, 28 Jul 2004 13:34:55 +0200	[thread overview]
Message-ID: <1091014495.2795.25.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20040728112222.GA7670@suse.de>

[-- Attachment #1: Type: text/plain, Size: 478 bytes --]

On Wed, 2004-07-28 at 13:22, Olaf Hering wrote:
> The ppc bootloader code will not compile with zlib debug enabled.
> printf was not defined. Tested with vmlinux.coff
> This patch was sent out earlier. Appearently it is not possible
> to use the generic zlib copy in linux/lib

actually it should be possible. Ok so it needs to be compiled as 32 bit,
but surely just #include-ing the /linux/lib version, or even better, a
few Makefile tricks should allow that, right ?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-07-28 11:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28 11:22 [PATCH] fix zlib debug in ppc boot header Olaf Hering
2004-07-28 11:34 ` Arjan van de Ven [this message]
2004-07-28 15:01   ` Tom Rini
2004-07-28 15:36     ` Olaf Hering
2004-07-28 23:06       ` Tom Rini
2004-07-29  6:48         ` Olaf Hering
2004-07-28 15:18 ` Geert Uytterhoeven
2004-07-28 15:29 ` Tom Rini
2004-07-28 17:42   ` Sam Ravnborg
2004-07-28 15:56     ` Tom Rini
2004-07-28 18:18       ` Sam Ravnborg
2004-07-28 16:39         ` Tom Rini
2004-07-28 16:47           ` Jörn Engel

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=1091014495.2795.25.camel@laptop.fenrus.com \
    --to=arjanv@redhat.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=olh@suse.de \
    --cc=trini@kernel.crashing.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