From: Eduardo Habkost <ehabkost@redhat.com>
To: Cao jin <caoj.fnst@cn.fujitsu.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
david@gibson.dropbear.id.au, qemu-devel@nongnu.org,
mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] correct comment of MemoryHotplugState
Date: Tue, 15 Mar 2016 17:00:24 -0300 [thread overview]
Message-ID: <20160315200024.GA26803@thinpad.lan.raisama.net> (raw)
In-Reply-To: <56E64F2E.8030201@cn.fujitsu.com>
On Mon, Mar 14, 2016 at 01:42:06PM +0800, Cao jin wrote:
> Hi,
> Is anyone gonna take this one?
Not sure which tree this should go. Michael, Igor, if you expect
this to go through the Machine Core tree, please let me know.
--
Eduardo
next prev parent reply other threads:[~2016-03-15 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 9:24 [Qemu-devel] [PATCH] correct comment of MemoryHotplugState Cao jin
2016-03-03 13:59 ` Igor Mammedov
2016-03-04 8:42 ` Cao jin
2016-03-14 5:42 ` Cao jin
2016-03-15 20:00 ` Eduardo Habkost [this message]
2016-04-09 9:18 ` Cao jin
2016-04-12 18:49 ` Eduardo Habkost
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=20160315200024.GA26803@thinpad.lan.raisama.net \
--to=ehabkost@redhat.com \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=david@gibson.dropbear.id.au \
--cc=imammedo@redhat.com \
--cc=mst@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).