From: Paolo Bonzini <pbonzini@redhat.com>
To: Liu Ping Fan <qemulist@gmail.com>
Cc: "Jan Kiszka" <jan.kiszka@siemens.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
qemu-devel@nongnu.org, "Anthony Liguori" <anthony@codemonkey.ws>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v4 0/3] bugs fix for hpet
Date: Tue, 03 Sep 2013 13:17:11 +0200 [thread overview]
Message-ID: <5225C537.1070109@redhat.com> (raw)
In-Reply-To: <1378105571-20570-1-git-send-email-pingfank@linux.vnet.ibm.com>
Il 02/09/2013 09:06, Liu Ping Fan ha scritto:
> note: I rebase it onto Stefan's net-next tree, since pc-1.7 has already been defined there.
>
> v4:
> use standard compat property to set hpet's interrupt compatibility
>
> v3:
> change hpet interrupt capablity on board's demand
>
>
> Liu Ping Fan (3):
> hpet: inverse polarity when pin above ISA_NUM_IRQS
> hpet: entitle more irq pins for hpet
> pc-1.6: add compatibility for hpet intcap on pc-*-1.6
>
> hw/timer/hpet.c | 27 +++++++++++++++++++++++----
> include/hw/i386/pc.h | 5 +++++
> 2 files changed, 28 insertions(+), 4 deletions(-)
>
Looks good. But I have one question; should this be changed for PIIX
too, or should the 1.7 PIIX machine keep the old behavior? (I have no
idea).
Paolo
next prev parent reply other threads:[~2013-09-03 11:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 7:06 [Qemu-devel] [PATCH v4 0/3] bugs fix for hpet Liu Ping Fan
2013-09-02 7:06 ` [Qemu-devel] [PATCH v4 1/3] hpet: inverse polarity when pin above ISA_NUM_IRQS Liu Ping Fan
2013-09-02 7:06 ` [Qemu-devel] [PATCH v4 2/3] hpet: entitle more irq pins for hpet Liu Ping Fan
2013-09-02 7:06 ` [Qemu-devel] [PATCH v4 3/3] pc-1.6: add compatibility for hpet intcap on pc-*-1.6 Liu Ping Fan
2013-09-02 11:41 ` [Qemu-devel] [PATCH v4 0/3] bugs fix for hpet Stefan Hajnoczi
2013-09-03 11:17 ` Paolo Bonzini [this message]
2013-09-04 5:29 ` liu ping fan
2013-09-04 7:03 ` Paolo Bonzini
2013-09-04 8:20 ` liu ping fan
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=5225C537.1070109@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=qemulist@gmail.com \
--cc=stefanha@redhat.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).