mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Woody Suwalski <woodys@xandros.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>
Subject: Re: x86: removing zImage support?
Date: Wed, 11 Mar 2009 17:39:36 +0000	[thread overview]
Message-ID: <1236793176.12283.255.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <49B7EEEA.3080203@zytor.com>

On Wed, 2009-03-11 at 10:03 -0700, H. Peter Anvin wrote:
> Woody Suwalski wrote:
> >>   
> > If x86-only - OK.
> > 
> > However zImage is the format used on ARM quite often... So any "kernel
> > complexity removal" need to happen only on x86 side.
> > 
> 
> I have no idea about ARM zImage... the whole zImage vs bzImage is pretty
> x86-specific in the first place, so yes, I was referring to x86
> specifically.

Is there any point in just making bzImage==zImage for x86?

I lost count of the number of times I've explained that bzImage has
nothing to do with bzip...

Ian.

-- 
Ian Campbell
Current Noise: Alice In Chains - Nutshell

Live free or die.


  reply	other threads:[~2009-03-11 17:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11  0:20 H. Peter Anvin
2009-03-11  1:15 ` Andi Kleen
2009-03-11  1:47   ` H. Peter Anvin
2009-03-11 10:24 ` Ingo Molnar
2009-03-11 11:03   ` Thomas Gleixner
2009-03-11 14:14 ` Woody Suwalski
2009-03-11 17:03   ` H. Peter Anvin
2009-03-11 17:39     ` Ian Campbell [this message]
2009-03-11 18:02       ` H. Peter Anvin
2009-03-11 18:06 ` [tip:x86/setup] x86: remove zImage support H. Peter Anvin
2009-03-12 17:45   ` Paul Bolle
2009-03-12 19:25     ` H. Peter Anvin
2009-03-12 19:28     ` H. Peter Anvin
2009-03-12 19:57     ` [tip:x86/setup] x86: remove additional vestiges of the zImage/bzImage split H. Peter Anvin

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=1236793176.12283.255.camel@zakaz.uk.xensource.com \
    --to=ijc@hellion.org.uk \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=woodys@xandros.com \
    --cc=x86@kernel.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

all inboxes | Powered by JetHome®