From: Gleb Natapov <gleb@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: [PATCH, RFC 1/4] mc146818: move hpet handling to pc.c
Date: Tue, 25 May 2010 08:31:49 +0300 [thread overview]
Message-ID: <20100525053149.GL22163@redhat.com> (raw)
In-Reply-To: <4BFADF8F.9050103@web.de>
On Mon, May 24, 2010 at 10:20:31PM +0200, Jan Kiszka wrote:
> > Maybe the coalescing should be pushed to APIC, or even generalized.
>
> The latter has happened, hopefully in the right direction.
>
What do you mean by that?
--
Gleb.
next prev parent reply other threads:[~2010-05-25 5:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 12:39 [Qemu-devel] [PATCH, RFC 1/4] mc146818: move hpet handling to pc.c Blue Swirl
2010-05-23 15:40 ` [Qemu-devel] " Jan Kiszka
2010-05-23 16:02 ` Blue Swirl
2010-05-24 15:30 ` Jan Kiszka
2010-05-24 19:58 ` Blue Swirl
2010-05-24 20:20 ` Jan Kiszka
2010-05-25 5:31 ` Gleb Natapov [this message]
2010-05-25 6:09 ` Jan Kiszka
2010-05-25 6:12 ` Gleb Natapov
2010-05-25 5:33 ` Gleb Natapov
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=20100525053149.GL22163@redhat.com \
--to=gleb@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@web.de \
--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).