From: Don Slutz <dslutz@verizon.com>
To: Don Slutz <dslutz@verizon.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Luiz Capitulino" <lcapitulino@redhat.com>,
"Anthony Liguori" <aliguori@amazon.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v2 0/7] Add limited support of VMware's hyper-call rpc
Date: Mon, 27 Apr 2015 19:28:56 -0400 [thread overview]
Message-ID: <553EC638.6050205@one.verizon.com> (raw)
In-Reply-To: <1430174764-19503-1-git-send-email-dslutz@verizon.com>
On 04/27/15 18:45, Don Slutz wrote:
> Changes v2 to v3:
>
> s/2.3/2.4
>
Opps, forgot to change all the subjects. Can re-send if requested.
-Don Slutz
> Changes v1 to v2:
>
next prev parent reply other threads:[~2015-04-27 23:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 22:45 [Qemu-devel] [PATCH v2 0/7] Add limited support of VMware's hyper-call rpc Don Slutz
2015-04-27 22:45 ` [Qemu-devel] [PATCH v2 1/7] vmport.c: Fix vmport_cmd_ram_size Don Slutz
2015-04-27 22:45 ` [Qemu-devel] [PATCH v2 2/7] vmport_rpc: Add the object vmport_rpc Don Slutz
2015-04-27 22:46 ` [Qemu-devel] [PATCH v2 3/7] vmport_rpc: Add limited support of VMware's hyper-call rpc Don Slutz
2015-04-27 22:46 ` [Qemu-devel] [PATCH v2 4/7] vmport_rpc: Add QMP access to vmport_rpc object Don Slutz
2015-04-28 8:13 ` Paolo Bonzini
2015-04-28 14:15 ` Don Slutz
2015-04-27 22:46 ` [Qemu-devel] [PATCH v2 5/7] vmport_rpc: Add migration Don Slutz
2015-04-27 22:46 ` [Qemu-devel] [PATCH v2 6/7] vmport: Add VMware all ring hack Don Slutz
2015-04-27 22:46 ` [Qemu-devel] [PATCH v2 7/7] MAINTAINERS: add VMware port Don Slutz
2015-04-27 23:28 ` Don Slutz [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-16 23:20 [Qemu-devel] [PATCH v2 0/7] Add limited support of VMware's hyper-call rpc Don Slutz
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=553EC638.6050205@one.verizon.com \
--to=dslutz@verizon.com \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).