From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>, "Lin Ma" <lma@suse.com>,
imammedo@redhat.com, peter.crosthwaite@xilinx.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v6 1/2] qom: Add can_be_deleted callback to UserCreatableClass
Date: Tue, 31 Mar 2015 12:51:26 +0200 [thread overview]
Message-ID: <551A7C2E.2010704@redhat.com> (raw)
In-Reply-To: <551A7B80.8090407@suse.de>
On 31/03/2015 12:48, Andreas Färber wrote:
> Am 30.03.2015 um 10:36 schrieb Lin Ma:
>> If backends implement the can_be_deleted and it returns false,
>> Then the qmp_object_del won't delete the given backends.
>>
>> Signed-off-by: Lin Ma <lma@suse.com>
>> ---
>> include/qom/object_interfaces.h | 13 +++++++++++++
>> qmp.c | 5 +++++
>> qom/object_interfaces.c | 12 ++++++++++++
>> 3 files changed, 30 insertions(+)
>
> Fine with me,
>
> Reviewed-by: Andreas Färber <afaerber@suse.de>
>
> I'm expecting this will go through Paolo's or QMP tree.
Yes, I'm waiting for some reviews on the ioport patches, otherwise I'll
send the pull request after -rc2 (don't want to send out unreviewed
patches hours before we ship it).
Paolo
next prev parent reply other threads:[~2015-03-31 10:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 8:36 [Qemu-devel] [PATCH v6 0/2] Add generic can_be_deleted to UserCreatableClass Lin Ma
2015-03-30 8:36 ` [Qemu-devel] [PATCH v6 1/2] qom: Add can_be_deleted callback " Lin Ma
2015-03-31 10:48 ` Andreas Färber
2015-03-31 10:51 ` Paolo Bonzini [this message]
2015-03-30 8:36 ` [Qemu-devel] [PATCH v6 2/2] hostmem: Prevent removing an in-use memory backend Lin Ma
2015-03-30 8:50 ` [Qemu-devel] [PATCH v6 0/2] Add generic can_be_deleted to UserCreatableClass Paolo Bonzini
2015-03-30 12:06 ` 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=551A7C2E.2010704@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=imammedo@redhat.com \
--cc=lma@suse.com \
--cc=peter.crosthwaite@xilinx.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).