From: Kevin O'Connor <kevin@koconnor.net>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
seabios@seabios.org, QEMU Developers <qemu-devel@nongnu.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: [Qemu-devel] Re: [PATCH] Seabios e820 reservation portion
Date: Mon, 15 Feb 2010 19:43:22 -0500 [thread overview]
Message-ID: <20100216004322.GD9677@morn.localdomain> (raw)
In-Reply-To: <4B798587.8080906@redhat.com>
On Mon, Feb 15, 2010 at 06:33:59PM +0100, Jes Sorensen wrote:
> Hi,
>
> This is the Seabios part to match my e820 reservation via fw_cfg patch.
This still has 'struct e820_entry' which is too similar to 'struct
e820entry' in memmap.h. Otherwise, it looks good to me.
-Kevin
next prev parent reply other threads:[~2010-02-16 0:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 17:33 [Qemu-devel] [PATCH] Seabios e820 reservation portion Jes Sorensen
2010-02-16 0:43 ` Kevin O'Connor [this message]
2010-02-16 8:46 ` [Qemu-devel] [PATCH] Seabios e820 reservation portion v3 Jes Sorensen
2010-02-21 19:18 ` [Qemu-devel] " Kevin O'Connor
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=20100216004322.GD9677@morn.localdomain \
--to=kevin@koconnor.net \
--cc=Jes.Sorensen@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.org \
--cc=stefano.stabellini@eu.citrix.com \
/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).