From: Eric Blake <eblake@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: gleb@kernel.org, pbonzini@redhat.com, qemu-devel@nongnu.org,
armbru@redhat.com, mprivozn@redhat.com
Subject: Re: [Qemu-devel] [patch 0/3] add QMP command to reset rtc interrupt backlog (v3)
Date: Mon, 02 Jun 2014 13:41:14 -0600 [thread overview]
Message-ID: <538CD35A.5010506@redhat.com> (raw)
In-Reply-To: <20140602192015.GA9999@amt.cnet>
[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]
On 06/02/2014 01:20 PM, Marcelo Tosatti wrote:
> On Mon, Jun 02, 2014 at 01:05:50PM -0600, Eric Blake wrote:
>> On 06/02/2014 11:51 AM, mtosatti@redhat.com wrote:
>>> It is necessary to reset RTC interrupt backlog if guest time is
>>> synchronized via a different mechanism, such as QGA's guest-set-time
>>> command.
>>>
>>> Failing to do so causes both corrections to be applied (summed),
>>> resulting in an incorrect guest time.
>>
>> Please send v3 of a series as a new top-level thread instead of buried
>> as a reply to v2.
>
> I prefer to delete whole threads i am not interested in.
>
> What is the problem with threads for you ?
Threads are good. But one thread per version of a series is better than
one thread for ALL versions of the series, as documented in our patch
submission guidelines:
http://wiki.qemu.org/Contribute/SubmitAPatch
Since most of contributors are already doing that, most reviewers have
gotten into the habit of assuming that any replies to a series are in
regards to things to fix, rather than looking for a new version of the
series. I'd rather kill several threads for versions of a series, then
later learn that a new revision of the series needs my review; than kill
a single thread, at which point I no longer see any new versions in my
inbox but also lose any chance to be easily pulled back in to that topic.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2014-06-02 19:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140530201145.194061806@amt.cnet>
2014-06-02 17:51 ` [Qemu-devel] [patch 0/3] add QMP command to reset rtc interrupt backlog (v3) mtosatti
2014-06-02 17:51 ` [Qemu-devel] [patch 1/3] mc146818rtc: add rtc_reset_reinjection QMP command mtosatti
2014-06-02 19:31 ` Eric Blake
2014-06-02 20:20 ` Marcelo Tosatti
2014-06-02 20:31 ` Eric Blake
2014-06-02 17:51 ` [Qemu-devel] [patch 2/3] add object_property_add_alias mtosatti
2014-06-02 17:51 ` [Qemu-devel] [patch 3/3] mc146818rtc: add "rtc" link to "/machine" mtosatti
2014-06-02 19:05 ` [Qemu-devel] [patch 0/3] add QMP command to reset rtc interrupt backlog (v3) Eric Blake
2014-06-02 19:20 ` Marcelo Tosatti
2014-06-02 19:41 ` Eric Blake [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=538CD35A.5010506@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=gleb@kernel.org \
--cc=mprivozn@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.