From: Kevin Wolf <kwolf@redhat.com>
To: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>,
Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PULL 00/14] QMP queue
Date: Tue, 14 Jan 2014 17:44:51 +0100 [thread overview]
Message-ID: <20140114164451.GE3320@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <5573dbe5-6e4f-46f8-a77a-85919645417e@TX2EHSMHS027.ehs.local>
Am 14.01.2014 um 04:38 hat Edgar E. Iglesias geschrieben:
> On Tue, Jan 14, 2014 at 09:27:10AM +1000, Peter Crosthwaite wrote:
> > Ping,
> >
> > Has this one been forgotten or are there issues? PMM had a small
> > comment, but he waived it AFAICT.
>
> Pong,
>
> I've merged it now, thanks!
I believe it's something in this pull requests that breaks make check.
Kevin
next prev parent reply other threads:[~2014-01-14 16:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 22:03 [Qemu-devel] [PULL 00/14] QMP queue Luiz Capitulino
2014-01-06 22:03 ` [Qemu-devel] [PULL 01/14] vl: add missing transition debug->finish_migrate Luiz Capitulino
2014-01-06 22:03 ` [Qemu-devel] [PULL 02/14] qemu-monitor: HMP cpu-add wrapper Luiz Capitulino
2014-01-06 22:03 ` [Qemu-devel] [PULL 03/14] rng: initialize file descriptor to -1 Luiz Capitulino
2014-01-06 22:03 ` [Qemu-devel] [PULL 04/14] qom: fix leak for objects created with -object Luiz Capitulino
2014-01-06 22:03 ` [Qemu-devel] [PULL 05/14] qom: catch errors in object_property_add_child Luiz Capitulino
2014-01-06 22:03 ` [Qemu-devel] [PULL 06/14] monitor: add object-del (QMP) and object_del (HMP) command Luiz Capitulino
2014-01-06 22:03 ` [Qemu-devel] [PULL 07/14] monitor: add object-add (QMP) and object_add " Luiz Capitulino
2014-01-06 22:03 ` [Qemu-devel] [PULL 08/14] error: Add error_abort Luiz Capitulino
2014-01-06 22:03 ` [Qemu-devel] [PULL 09/14] qdev: Delete dead code Luiz Capitulino
2014-01-06 22:03 ` [Qemu-devel] [PULL 10/14] hw: Remove assert_no_error usages Luiz Capitulino
2014-01-06 22:03 ` [Qemu-devel] [PULL 11/14] target-i386: Remove assert_no_error usage Luiz Capitulino
2014-01-06 22:03 ` [Qemu-devel] [PULL 12/14] qemu-option: Remove qemu_opts_create_nofail Luiz Capitulino
2014-01-06 22:03 ` [Qemu-devel] [PULL 13/14] qerror: Remove assert_no_error() Luiz Capitulino
2014-01-06 22:03 ` [Qemu-devel] [PULL 14/14] migration: qmp_migrate(): keep working after syntax error Luiz Capitulino
2014-01-06 22:41 ` [Qemu-devel] [PULL 00/14] QMP queue Peter Maydell
2014-01-13 23:27 ` Peter Crosthwaite
2014-01-14 3:38 ` Edgar E. Iglesias
2014-01-14 16:44 ` Kevin Wolf [this message]
2014-01-14 18:22 ` [Qemu-devel] Fix make check breakage (was [PULL 00/14] QMP queue) Luiz Capitulino
2014-01-14 22:26 ` Peter Crosthwaite
2014-01-15 0:30 ` Peter Crosthwaite
2014-01-15 9:55 ` Markus Armbruster
2014-01-15 12:27 ` Peter Crosthwaite
2014-01-15 13:52 ` Markus Armbruster
-- strict thread matches above, loose matches on Subject: below --
2012-01-18 17:41 [Qemu-devel] [PULL 00/14]: QMP queue Luiz Capitulino
2012-01-19 18:47 ` Anthony Liguori
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=20140114164451.GE3320@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=aliguori@amazon.com \
--cc=anthony@codemonkey.ws \
--cc=edgar.iglesias@xilinx.com \
--cc=lcapitulino@redhat.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).