From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56285) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YUxLD-0003us-Bn for qemu-devel@nongnu.org; Mon, 09 Mar 2015 09:03:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YUxL7-0002kA-Ly for qemu-devel@nongnu.org; Mon, 09 Mar 2015 09:03:27 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45991) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YUxL7-0002jo-EW for qemu-devel@nongnu.org; Mon, 09 Mar 2015 09:03:21 -0400 Date: Mon, 9 Mar 2015 09:03:16 -0400 From: Luiz Capitulino Message-ID: <20150309090316.6cafa891@redhat.com> In-Reply-To: References: <1425496415-6161-1-git-send-email-lcapitulino@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PULL 0/5] QMP queue List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: QEMU Developers On Sun, 8 Mar 2015 23:08:04 +0900 Peter Maydell wrote: > On 5 March 2015 at 04:13, Luiz Capitulino wrote: > > Hi, > > > > This pull request contains two series. A balloon series and memory hotplug > > doc series. The balloon series is not totally QMP related, but it has > > implications to libvirt when using memory hotplug. So, I'm picking it up. > > The second series is a memory hotplug doc improvement. This is not QMP > > related at all, but I'm adding it here as it got fully reviewed and is > > really wanted. > > > > The following changes since commit 3539bbb93e944ffde31c61c369ea9eedcc5697a6: > > > > Merge remote-tracking branch 'remotes/awilliam/tags/vfio-update-20150302.0' into staging (2015-03-04 14:37:31 +0000) > > > > are available in the git repository at: > > > > > > git://repo.or.cz/qemu/qmp-unstable.git queue/qmp > > > > for you to fetch changes up to a3b042179859c68b3d08f8aa43866d28d6b56987: > > > > docs: add memory-hotplug.txt (2015-03-04 13:00:36 -0500) > > Nudge: this isn't a signed pull request. I'm not currently rejecting > unsigned pulls, but at some point in the not very distant future > (maybe after 2.3?) I plan to start doing so... My bad. I knew there was something missing when I was fixing my scripts after a long time without sending pull requests. Sorry about that. > That said, I've applied this to master. Thanks.