qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Markus Armbruster" <armbru@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH 0/2] tests: A few check-qom-proplist fixes
Date: Tue, 25 Oct 2016 16:40:47 -0200	[thread overview]
Message-ID: <20161025184047.GA20882@thinpad.lan.raisama.net> (raw)
In-Reply-To: <20161017210237.GB3275@thinpad.lan.raisama.net>

Pinging again.

On Mon, Oct 17, 2016 at 07:02:37PM -0200, Eduardo Habkost wrote:
> Ping?
> 
> Markus, do you want to merge this through your tree?
> 
> On Tue, Oct 11, 2016 at 09:37:45AM -0300, Eduardo Habkost wrote:
> > A few fixes on check-qom-proplist that will ensure we test both
> > class properties and object properties, and catch errors when
> > registering properties in test code.
> > 
> > Eduardo Habkost (2):
> >   tests: check-qom-proplist: Remove "bv" class property from class
> >   tests: check-qom-proplist: Use &error_abort to catch errors
> > 
> >  tests/check-qom-proplist.c | 10 +++-------
> >  1 file changed, 3 insertions(+), 7 deletions(-)
> > 
> > -- 
> > 2.7.4
> > 
> 
> -- 
> Eduardo
> 

-- 
Eduardo

  parent reply	other threads:[~2016-10-25 18:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11 12:37 [Qemu-devel] [PATCH 0/2] tests: A few check-qom-proplist fixes Eduardo Habkost
2016-10-11 12:37 ` [Qemu-devel] [PATCH 1/2] tests: check-qom-proplist: Remove "bv" class property from class Eduardo Habkost
2016-10-11 12:39   ` Daniel P. Berrange
2016-10-11 12:37 ` [Qemu-devel] [PATCH 2/2] tests: check-qom-proplist: Use &error_abort to catch errors Eduardo Habkost
2016-10-11 12:40   ` Daniel P. Berrange
2016-10-17 21:02 ` [Qemu-devel] [PATCH 0/2] tests: A few check-qom-proplist fixes Eduardo Habkost
2016-10-17 22:07   ` Andreas Färber
2016-10-18 13:58     ` Eduardo Habkost
2016-10-25 18:40   ` Eduardo Habkost [this message]
2016-11-03 16:51 ` 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=20161025184047.GA20882@thinpad.lan.raisama.net \
    --to=ehabkost@redhat.com \
    --cc=afaerber@suse.de \
    --cc=armbru@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).