qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
To: qemu-devel@nongnu.org
Cc: hutao@cn.fujitsu.com, tangchen@cn.fujitsu.com,
	isimatu.yasuaki@jp.fujitsu.com, aliguori@amazon.com,
	lcapitulino@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v1 0/3] monitor: add peripheral device del completion support
Date: Fri, 26 Sep 2014 10:01:48 +0800	[thread overview]
Message-ID: <1411696908.4138.0.camel@G08FNSTD140041> (raw)
In-Reply-To: <cover.1411019133.git.zhugh.fnst@cn.fujitsu.com>

ping ...

On Thu, 2014-09-18 at 15:53 +0800, Zhu Guihua wrote:
> After inputting device_del command in monitor, we expect to list all
> hotpluggable devices automatically by pressing tab key. This patchset provides
> the function to list all peripheral devices such as memory devices.
> 
> Zhu Guihua (3):
>   qom: add function to get opaque property in ObjectProperty
>   qom: export object_property_is_child()
>   monitor: add del completion for peripheral device
> 
>  include/qom/object.h |  2 ++
>  monitor.c            | 24 ++++++++++++++++++++++++
>  qom/object.c         | 11 ++++++++++-
>  3 files changed, 36 insertions(+), 1 deletion(-)
> 

      parent reply	other threads:[~2014-09-26  2:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18  7:53 [Qemu-devel] [PATCH v1 0/3] monitor: add peripheral device del completion support Zhu Guihua
2014-09-18  7:53 ` [Qemu-devel] [PATCH v1 1/3] qom: add function to get opaque property in ObjectProperty Zhu Guihua
2014-09-18  7:53 ` [Qemu-devel] [PATCH v1 2/3] qom: export object_property_is_child() Zhu Guihua
2014-09-26  9:31   ` Andreas Färber
2014-09-18  7:53 ` [Qemu-devel] [PATCH v1 3/3] monitor: add del completion for peripheral device Zhu Guihua
2014-09-26  9:29   ` Andreas Färber
2014-09-26 17:25   ` Luiz Capitulino
2014-09-26 17:29     ` Luiz Capitulino
2014-09-29 21:33       ` Hani Benhabiles
2014-09-26  2:01 ` Zhu Guihua [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=1411696908.4138.0.camel@G08FNSTD140041 \
    --to=zhugh.fnst@cn.fujitsu.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=hutao@cn.fujitsu.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tangchen@cn.fujitsu.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).