From: Peter Maydell <peter.maydell@linaro.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Cornelia Huck" <cornelia.huck@de.ibm.com>,
"Alexander Graf" <agraf@suse.de>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] qdev: Deprecated qdev_init() is finally unused, drop
Date: Thu, 12 Mar 2015 15:10:42 +0000 [thread overview]
Message-ID: <CAFEAcA_FdA1_J4toQf=7FBS0WKXTNm_pe2TnEqOTQ24L5dMt3A@mail.gmail.com> (raw)
In-Reply-To: <1426172059-12237-1-git-send-email-armbru@redhat.com>
On 12 March 2015 at 14:54, Markus Armbruster <armbru@redhat.com> wrote:
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> Depends on
> [PATCH 3/3] s390x: Replace unchecked qdev_init() by qdev_init_nofail()
> [PATCH] macio: Convert to realize()
Always nice to remove a deprecated API...
> --- a/include/hw/qdev-core.h
> +++ b/include/hw/qdev-core.h
> @@ -66,7 +66,7 @@ struct VMStateDescription;
> * After successful realization, setting static properties will fail.
> *
> * As an interim step, the #DeviceState:realized property is set by deprecated
> - * functions qdev_init() and qdev_init_nofail().
> + * function qdev_init_nofail().
> * In the future, devices will propagate this state change to their children
> * and along busses they expose.
> * The point in time will be deferred to machine creation, so that values
So is the non-deprecated approach to have the board call
object_property_set_bool(OBJECT(dev), true, "realized", &err);
directly itself (handling errors however it feels like) rather
than calling qdev_init_nofail() ?
-- PMM
next prev parent reply other threads:[~2015-03-12 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 14:54 [Qemu-devel] [PATCH] qdev: Deprecated qdev_init() is finally unused, drop Markus Armbruster
2015-03-12 15:10 ` Peter Maydell [this message]
2015-03-12 15:18 ` Paolo Bonzini
2015-03-12 15:45 ` 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='CAFEAcA_FdA1_J4toQf=7FBS0WKXTNm_pe2TnEqOTQ24L5dMt3A@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=cornelia.huck@de.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).