From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Igor Mammedov <imammedo@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH qom-next 0/2] qdev-monitor: Reference counting follow-ups
Date: Mon, 07 Oct 2013 19:04:47 +0200 [thread overview]
Message-ID: <5252E9AF.6010606@redhat.com> (raw)
In-Reply-To: <1381164241-6566-1-git-send-email-afaerber@suse.de>
Il 07/10/2013 18:43, Andreas Färber ha scritto:
> Hello,
>
> I have queued bug fixes by Igor and Stefan for device_add on qom-next and
> am rearranging the following changes of mine on top.
>
> 1) Further naming cleanups, now rebased on the bugfixes for easier backporting.
> 2) Inlining of qdev_init(), so that we always have unparent+unref pairs.
>
> If there's no objections, planning to include this in a pull tonight or tomorrow.
>
> Regards,
> Andreas
>
> Cc: Igor Mammedov <imammedo@redhat.com>
> Cc: Stefan Hajnoczi <stefanha@redhat.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Anthony Liguori <anthony@codemonkey.ws>
>
> Andreas Färber (2):
> qdev-monitor: Avoid qdev as variable name
> qdev-monitor: Inline qdev_init() for device_add
>
> qdev-monitor.c | 37 +++++++++++++++++++++----------------
> 1 file changed, 21 insertions(+), 16 deletions(-)
>
Yes, looks good.
Paolo
next prev parent reply other threads:[~2013-10-07 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 16:43 [Qemu-devel] [PATCH qom-next 0/2] qdev-monitor: Reference counting follow-ups Andreas Färber
2013-10-07 16:44 ` [Qemu-devel] [PATCH qom-next 1/2] qdev-monitor: Avoid qdev as variable name Andreas Färber
2013-10-07 16:44 ` [Qemu-devel] [PATCH qom-next 2/2] qdev-monitor: Inline qdev_init() for device_add Andreas Färber
2013-10-07 17:04 ` Paolo Bonzini [this message]
2013-10-08 8:37 ` [Qemu-devel] [PATCH qom-next 0/2] qdev-monitor: Reference counting follow-ups Igor Mammedov
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=5252E9AF.6010606@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=imammedo@redhat.com \
--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).