From: Marcelo Tosatti <mtosatti@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Gleb Natapov <gleb@redhat.com>
Subject: [Qemu-devel] [PATCH] correct RTC_CHANGE_EVENT description (v2)
Date: Fri, 7 Jun 2013 16:52:43 -0300 [thread overview]
Message-ID: <20130607195243.GA13357@amt.cnet> (raw)
In-Reply-To: <20130603081830.44a7ed1f@redhat.com>
Fix RTC_CHANGE event description to match implementation.
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
diff --git a/QMP/qmp-events.txt b/QMP/qmp-events.txt
index 92fe5fb..24e804e9 100644
--- a/QMP/qmp-events.txt
+++ b/QMP/qmp-events.txt
@@ -203,7 +203,8 @@ Emitted when the guest changes the RTC time.
Data:
-- "offset": delta against the host UTC in seconds (json-number)
+- "offset": Offset between base RTC clock (as specified by -rtc base), and
+new RTC clock value (json-number)
Example:
next prev parent reply other threads:[~2013-06-07 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 18:24 [Qemu-devel] [PATCH] correct RTC_CHANGE_EVENT description Marcelo Tosatti
2013-06-03 12:18 ` Luiz Capitulino
2013-06-07 19:52 ` Marcelo Tosatti [this message]
2013-06-07 21:03 ` [Qemu-devel] [PATCH] correct RTC_CHANGE_EVENT description (v2) Luiz Capitulino
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=20130607195243.GA13357@amt.cnet \
--to=mtosatti@redhat.com \
--cc=gleb@redhat.com \
--cc=lcapitulino@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).