From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH 0/5] allow arbitrary scaling of timers
Date: Mon, 14 Mar 2011 08:14:06 +0100 [thread overview]
Message-ID: <4D7DC03E.3080202@redhat.com> (raw)
In-Reply-To: <4D7C02B6.3000503@codemonkey.ws>
On 03/13/2011 12:33 AM, Anthony Liguori wrote:
>
> Really nice series.
>
> The whole thing Reviewed-by: Anthony Liguori <aliguori@us.ibm.com>
>
> Did you really mean to RFC this? I don't think there's any sort of
> problem applying this as it's mostly mechanical.
Yeah, it's just that the topic had been brought before and other people
may have other ideas regarding the API. It's something pretty central
so the API change warranted an RFC. If you want to apply it, now or in
a few days, I certainly won't complain.
Paolo
next prev parent reply other threads:[~2011-03-14 7:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 17:04 [Qemu-devel] [RFC PATCH 0/5] allow arbitrary scaling of timers Paolo Bonzini
2011-03-12 17:04 ` [Qemu-devel] [RFC PATCH 1/5] add more helper functions with explicit milli/nanosecond resolution Paolo Bonzini
2011-03-12 17:04 ` [Qemu-devel] [RFC PATCH 2/5] change all rt_clock references to use millisecond resolution accessors Paolo Bonzini
2011-03-12 17:04 ` [Qemu-devel] [RFC PATCH 3/5] change all other clock references to use nanosecond " Paolo Bonzini
2011-03-12 17:04 ` [Qemu-devel] [RFC PATCH 4/5] add a generic scaling mechanism for timers Paolo Bonzini
2011-03-12 17:04 ` [Qemu-devel] [RFC PATCH 5/5] remove qemu_get_clock Paolo Bonzini
2011-03-12 23:33 ` [Qemu-devel] [RFC PATCH 0/5] allow arbitrary scaling of timers Anthony Liguori
2011-03-14 7:14 ` Paolo Bonzini [this message]
2011-03-21 13:35 ` [Qemu-devel] [PULL] " Paolo Bonzini
2011-03-21 20:44 ` Aurelien Jarno
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=4D7DC03E.3080202@redhat.com \
--to=pbonzini@redhat.com \
--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).