From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Marcel Apfelbaum" <marcel@redhat.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [RFC PATCH 0/3] add helpers to be more explicit when using QOM abstract parent hooks
Date: Mon, 15 Jan 2018 12:08:55 +0100 [thread overview]
Message-ID: <250b835d-8f13-4dfe-1720-e889046dd9a3@redhat.com> (raw)
In-Reply-To: <20180114020412.26160-1-f4bug@amsat.org>
On 14/01/2018 03:04, Philippe Mathieu-Daudé wrote:
> Hi,
>
> Learning how to implement QOM devices I found the pattern changing parent hooks
> when the parent is abstract not trivial to understand.
>
> This series add few helpers to have this pattern more explicit.
>
> Those functions deserve some comments, but before spending more time I'd like
> to get some feedbacks if this might be useful or not.
> If so, I can split the 3rd patch in many patches for each subsystem maintainers.
>
> This can also be use for the CPUClass->reset() method, dunno if useful but
> maybe to be consistent.
Queued, thanks.
Paolo
prev parent reply other threads:[~2018-01-15 11:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 2:04 [Qemu-devel] [RFC PATCH 0/3] add helpers to be more explicit when using QOM abstract parent hooks Philippe Mathieu-Daudé
2018-01-14 2:04 ` [Qemu-devel] [RFC PATCH 1/3] qdev: rename typedef qdev_resetfn() -> DeviceReset() Philippe Mathieu-Daudé
2018-01-15 9:45 ` Laurent Vivier
2018-01-14 2:04 ` [Qemu-devel] [RFC PATCH 2/3] qdev: add helpers to be more explicit when using abstract QOM parent functions Philippe Mathieu-Daudé
2018-01-15 9:41 ` Laurent Vivier
2018-01-14 2:04 ` [Qemu-devel] [RFC PATCH 3/3] qdev: use device_class_set_parent_realize/unrealize/reset() Philippe Mathieu-Daudé
2018-01-15 1:42 ` David Gibson
2018-01-15 9:09 ` [Qemu-devel] [qemu-s390x] " Cornelia Huck
2018-01-15 9:35 ` [Qemu-devel] " Laurent Vivier
2018-01-15 9:48 ` Marcel Apfelbaum
2018-01-15 11:08 ` Paolo Bonzini [this message]
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=250b835d-8f13-4dfe-1720-e889046dd9a3@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=marcel@redhat.com \
--cc=mdroth@linux.vnet.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).