All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: Mark McLoughlin <markmc@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCHv3 1/3] x86: use ELF format in compressed images.
Date: Fri, 15 Feb 2008 08:10:02 +1100	[thread overview]
Message-ID: <47B4AE2A.6080300@goop.org> (raw)
In-Reply-To: <1203011834.30565.8.camel@cthulhu.hellion.org.uk>

Ian Campbell wrote:
> On Thu, 2008-02-14 at 17:01 +0000, Ian Campbell wrote:
>   
>> I have a xen domain builder patch as well. I was waiting for the Linux
>> side to gain some traction before putting it forward (I'd attach it
>> now but it's at home on a laptop which is sleeping).
>>     
>
> Here it is:
>
> # HG changeset patch
> # User ijc@hellion.org.uk
> # Date 1203011758 0
> # Node ID 3079b4b3835e3aba52bb6548bbbced70471a9f32
> # Parent  42369d21641d6297dc369441c3bfd355880d28c0
> Support loading Linux bzImage v2.08 and up.
>   

Do you also have a patch to update the boot protocol?

    J

  reply	other threads:[~2008-02-14 21:12 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 20:54 [PATCHv3 0/3] x86: boot protocol updates Ian Campbell
2008-02-13 20:54 ` [PATCHv3 1/3] x86: use ELF format in compressed images Ian Campbell
2008-02-13 20:54 ` Ian Campbell
2008-02-13 20:54   ` [PATCHv3 2/3] x86: add a crc32 checksum to the kernel image Ian Campbell
2008-02-13 20:55   ` [PATCHv3 3/3] x86: bump image header to version 2.08 Ian Campbell
2008-02-14 11:34   ` [PATCHv3 1/3] x86: use ELF format in compressed images Mark McLoughlin
2008-02-14 17:01     ` Ian Campbell
2008-02-14 17:37       ` Mark McLoughlin
2008-02-14 17:37       ` Mark McLoughlin
2008-02-14 17:51         ` Ian Campbell
2008-02-14 17:51         ` Ian Campbell
2008-02-14 17:57       ` Ian Campbell
2008-02-14 21:10         ` Jeremy Fitzhardinge [this message]
2008-02-14 21:14           ` H. Peter Anvin
2008-02-14 21:14           ` H. Peter Anvin
2008-02-15  6:37             ` Jeremy Fitzhardinge
2008-02-15  6:37             ` Jeremy Fitzhardinge
2008-02-14 21:10         ` Jeremy Fitzhardinge
2008-02-14 17:57       ` Ian Campbell
2008-02-14 18:29       ` Ian Campbell
2008-02-14 18:29       ` Ian Campbell
2008-02-14 18:30       ` H. Peter Anvin
2008-02-14 18:30       ` H. Peter Anvin
2008-02-14 17:01     ` Ian Campbell
2008-02-14 11:34   ` Mark McLoughlin
2008-04-06  7:03   ` Yinghai Lu
2008-04-06  7:03   ` Yinghai Lu
2008-04-06 10:22     ` Ian Campbell
2008-04-06 10:22     ` Ian Campbell
2008-04-06 16:38     ` H. Peter Anvin
2008-04-06 16:38     ` H. Peter Anvin
2008-04-06 17:19       ` Yinghai Lu
2008-04-06 17:19       ` Yinghai Lu
2008-04-06 17:25         ` H. Peter Anvin
2008-04-06 17:34           ` Yinghai Lu
2008-04-06 17:34           ` Yinghai Lu
2008-04-06 17:25         ` H. Peter Anvin
2008-02-17 14:04 ` [PATCHv3 0/3] x86: boot protocol updates Thomas Gleixner
2008-02-19  8:16   ` Ian Campbell

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=47B4AE2A.6080300@goop.org \
    --to=jeremy@goop.org \
    --cc=hpa@zytor.com \
    --cc=ijc@hellion.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markmc@redhat.com \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=virtualization@lists.linux-foundation.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.