From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: afaerber@suse.de, stefanha@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/2] qdev-monitor-test: Simplify & make more robust
Date: Thu, 6 Mar 2014 10:12:51 +0100 [thread overview]
Message-ID: <1394097173-14432-1-git-send-email-armbru@redhat.com> (raw)
Stefan's patch has been rotting on the list since December. Reposting
it together with a patch for a robustness issue I spotted when
reviewing it.
Markus Armbruster (1):
qdev-monitor-test: Don't test human-readable error message
Stefan Hajnoczi (1):
qdev-monitor-test: simplify using g_assert_cmpstr()
tests/qdev-monitor-test.c | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
--
1.8.1.4
next reply other threads:[~2014-03-06 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 9:12 Markus Armbruster [this message]
2014-03-06 9:12 ` [Qemu-devel] [PATCH v2 1/2] qdev-monitor-test: simplify using g_assert_cmpstr() Markus Armbruster
2014-03-06 9:12 ` [Qemu-devel] [PATCH v2 2/2] qdev-monitor-test: Don't test human-readable error message Markus Armbruster
2014-03-06 16:26 ` [Qemu-devel] [PATCH v2 0/2] qdev-monitor-test: Simplify & make more robust Eric Blake
2014-03-06 16:55 ` Stefan Hajnoczi
2014-03-06 19:16 ` Andreas Färber
2014-03-07 9:59 ` Markus Armbruster
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=1394097173-14432-1-git-send-email-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=afaerber@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).