From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] Improve rtc-test coverage
Date: Sat, 02 Feb 2013 13:17:20 +0100 [thread overview]
Message-ID: <510D03D0.9060407@redhat.com> (raw)
In-Reply-To: <1357922817-17584-1-git-send-email-pbonzini@redhat.com>
Il 11/01/2013 17:46, Paolo Bonzini ha scritto:
> Trying (unsuccessfully) to break the code and reproduce the effects
> of https://bugs.launchpad.net/qemu/+bug/1090558... Well, more
> tests never hurt...
>
> Paolo Bonzini (2):
> rtc-test: always set register B in its entirety
> rtc-test: add testcases for alarms in 12hour mode
>
> tests/rtc-test.c | 238 ++++++++++++++++++++++++++++++++++++++++++++++++-------
> 1 file changed, 208 insertions(+), 30 deletions(-)
>
Ping?
Paolo
prev parent reply other threads:[~2013-02-02 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 16:46 [Qemu-devel] [PATCH 0/2] Improve rtc-test coverage Paolo Bonzini
2013-01-11 16:46 ` [Qemu-devel] [PATCH 1/2] rtc-test: always set register B in its entirety Paolo Bonzini
2013-01-11 16:46 ` [Qemu-devel] [PATCH 2/2] rtc-test: add testcases for alarms in 12hour mode Paolo Bonzini
2013-02-02 12:17 ` Paolo Bonzini [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=510D03D0.9060407@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@us.ibm.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).