From: Paolo Bonzini <pbonzini@redhat.com>
To: "Eric Blake" <eblake@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
qemu-devel@nongnu.org
Cc: berrange@redhat.com, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 3/4] qobject: replace qobject_incref/QINCREF qobject_decref/QDECREF
Date: Fri, 13 Apr 2018 18:13:32 +0200 [thread overview]
Message-ID: <79dc3c32-32fe-316c-1874-779caf9a0e39@redhat.com> (raw)
In-Reply-To: <b041bde4-b926-2ede-d8a5-4721dafe6736@redhat.com>
On 29/03/2018 18:23, Eric Blake wrote:
>>
>> +/**
>> + * qobject_ref(): Increment QObject's reference count
>> + */
>> +#define qobject_ref(obj) \
>> + qobject_ref(QOBJECT(obj))
>
> ...below the functions of the same name. C preprocessor rules guarantee
> that you don't get infinite expansion, although I did a double-take the
> first time I read through the patch (especially since your v2 used the
> name qobject_ref_impl() for the function, distinct from the macro name).
> Worth a comment?
I prefer qobject_ref_impl, FWIW. There are already a few examples in
include/qemu/thread.h and include/qemu/coroutine.h.
Thanks,
Paolo
next prev parent reply other threads:[~2018-04-13 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 15:48 [Qemu-devel] [PATCH v3 0/4] RFC: simplify qobject refcount Marc-André Lureau
2018-03-29 15:48 ` [Qemu-devel] [PATCH v3 1/4] qobject: ensure base is at offset 0 Marc-André Lureau
2018-03-29 15:48 ` [Qemu-devel] [PATCH v3 2/4] qobject: introduce QObjectCommon Marc-André Lureau
2018-03-29 16:15 ` Eric Blake
2018-03-29 15:48 ` [Qemu-devel] [PATCH v3 3/4] qobject: replace qobject_incref/QINCREF qobject_decref/QDECREF Marc-André Lureau
2018-03-29 16:23 ` Eric Blake
2018-04-13 16:13 ` Paolo Bonzini [this message]
2018-03-29 15:48 ` [Qemu-devel] [PATCH v3 4/4] qobject: modify qobject_ref() to assert on NULL and return obj Marc-André Lureau
2018-03-29 16:10 ` Eric Blake
2018-04-13 16:05 ` Marc-André Lureau
2018-03-31 6:26 ` [Qemu-devel] [PATCH v3 0/4] RFC: simplify qobject refcount no-reply
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=79dc3c32-32fe-316c-1874-779caf9a0e39@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=marcandre.lureau@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).