qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: kvm <kvm@vger.kernel.org>, Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Blue Swirl <blauwirbel@gmail.com>, Avi Kivity <avi@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 0/7] pit, hpet, pcspk: fixes & preparation for KVM
Date: Fri, 17 Feb 2012 12:15:00 -0600	[thread overview]
Message-ID: <4F3E9924.8070904@us.ibm.com> (raw)
In-Reply-To: <cover.1328124701.git.jan.kiszka@siemens.com>

On 02/01/2012 01:31 PM, Jan Kiszka wrote:
> Changes in V4:
>   - rebased over qom-upstream.13
>   - comment on rtc_irq_level clearing on reset
>   - fix call to isa_register_ioport by passing the pcspk device
>
> Not changed:
>   - PIT pointer property of pcspk
>     (Paolo will port it together with other PROP_PTR users)
>
> CC: Paolo Bonzini<pbonzini@redhat.com>

Applied.  Thanks.

Regards,

Anthony Liguori

>
> Jan Kiszka (7):
>    i8254: Do not raise IRQ level on reset
>    hpet: Save/restore cached RTC IRQ level
>    i8254: Factor out interface header
>    i8254: Pass alternative IRQ output object on initialization
>    i8254: Rework&  fix interaction with HPET in legacy mode
>    pcspk: Convert to qdev
>    i8254: Factor out pit_get_channel_info
>
>   arch_init.c        |    1 +
>   hw/alpha_dp264.c   |    3 +-
>   hw/hpet.c          |   68 ++++++++++++++++++++++++++++----------
>   hw/hpet_emul.h     |    3 ++
>   hw/i82378.c        |    6 ++-
>   hw/i8254.c         |   92 ++++++++++++++++++++++-----------------------------
>   hw/i8254.h         |   57 ++++++++++++++++++++++++++++++++
>   hw/mips_fulong2e.c |    3 +-
>   hw/mips_jazz.c     |    6 ++-
>   hw/mips_malta.c    |    3 +-
>   hw/mips_r4k.c      |    3 +-
>   hw/pc.c            |   19 ++++++++--
>   hw/pc.h            |   29 ----------------
>   hw/pcspk.c         |   84 +++++++++++++++++++++++++++++++++++++++--------
>   hw/pcspk.h         |   45 +++++++++++++++++++++++++
>   15 files changed, 296 insertions(+), 126 deletions(-)
>   create mode 100644 hw/i8254.h
>   create mode 100644 hw/pcspk.h
>

      parent reply	other threads:[~2012-02-17 18:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 19:31 [Qemu-devel] [PATCH v4 0/7] pit, hpet, pcspk: fixes & preparation for KVM Jan Kiszka
2012-02-01 19:31 ` [Qemu-devel] [PATCH v4 1/7] i8254: Do not raise IRQ level on reset Jan Kiszka
2012-02-01 19:31 ` [Qemu-devel] [PATCH v4 2/7] hpet: Save/restore cached RTC IRQ level Jan Kiszka
2012-02-01 19:31 ` [Qemu-devel] [PATCH v4 3/7] i8254: Factor out interface header Jan Kiszka
2012-02-01 19:31 ` [Qemu-devel] [PATCH v4 4/7] i8254: Pass alternative IRQ output object on initialization Jan Kiszka
2012-02-01 19:31 ` [Qemu-devel] [PATCH v4 5/7] i8254: Rework & fix interaction with HPET in legacy mode Jan Kiszka
2012-02-01 19:31 ` [Qemu-devel] [PATCH v4 6/7] pcspk: Convert to qdev Jan Kiszka
2012-02-17 10:24   ` [Qemu-devel] [PATCH v5 " Jan Kiszka
2012-02-01 19:31 ` [Qemu-devel] [PATCH v4 7/7] i8254: Factor out pit_get_channel_info Jan Kiszka
2012-02-17 18:15 ` Anthony Liguori [this message]

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=4F3E9924.8070904@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.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).