From: Erik de Castro Lopo <mle+tools@mega-nerd.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Add handling of edge triggered interrupts in function pic_irq_request.
Date: Thu, 15 May 2008 20:37:18 +1000 [thread overview]
Message-ID: <20080515203718.0983979e.mle+tools@mega-nerd.com> (raw)
In-Reply-To: <20080515193204.cff99c8a.mle+tools@mega-nerd.com>
Erik de Castro Lopo wrote:
>
> This fixes a regression that prevents Win XP64 from installing and running
> under Qemu. The original breakage happened in the transition fron SVN
> revision 3371 to 3372.
Sorry, this patch needs more testing.
Erik
--
-----------------------------------------------------------------
Erik de Castro Lopo
-----------------------------------------------------------------
Greenspun's Tenth Rule: Any sufficiently complicated C or
Fortran program contains an ad hoc informally-specified
bug-ridden slow implementation of half of Common Lisp.
next prev parent reply other threads:[~2008-05-15 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 9:32 [Qemu-devel] Add handling of edge triggered interrupts in function pic_irq_request Erik de Castro Lopo
2008-05-15 10:37 ` Erik de Castro Lopo [this message]
2008-05-15 11:27 ` [Qemu-devel] [Patch] " Erik de Castro Lopo
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=20080515203718.0983979e.mle+tools@mega-nerd.com \
--to=mle+tools@mega-nerd.com \
--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).