From: Volker Ruppert <info@vruppert.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6110] Add patch to allow Bochs patch queue to be built from another directory.
Date: Thu, 25 Dec 2008 18:17:14 +0100 [thread overview]
Message-ID: <200812251817.14728.info@vruppert.de> (raw)
In-Reply-To: <494D9B3D.7060507@codemonkey.ws>
Hi all!
> Fantastic! I was planning on patch bombing the whole series to
> bochs-devel soon but this works too. Do you have any comments on #2,
> #3, or #5? #3 and #5 are guarded in BX_QEMU so they should be safe
> (although both could be useful to Bochs).
>
> #4 enables the e820 map to describe more than 4GB of memory. It's
> equally applicable to Bochs even if Bochs doesn't support this feature.
I have now applied the outstanding patches to the Bochs BIOS.
--
Thanks
Volker
next prev parent reply other threads:[~2008-12-25 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 18:59 [Qemu-devel] [6110] Add patch to allow Bochs patch queue to be built from another directory Anthony Liguori
2008-12-20 14:38 ` Volker Ruppert
2008-12-21 1:26 ` Anthony Liguori
2008-12-25 17:17 ` Volker Ruppert [this message]
2008-12-21 16:24 ` [Qemu-devel] Re: [6110] Add patch to allow Bochs patch queue to bebuilt " Sebastian Herbszt
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=200812251817.14728.info@vruppert.de \
--to=info@vruppert.de \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.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).