From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [Qemu-commits] [COMMIT ddd9bbd] Support for multiple -monitor devices
Date: Wed, 09 Sep 2009 14:42:32 +0300 [thread overview]
Message-ID: <4AA794A8.30401@redhat.com> (raw)
In-Reply-To: <4AA7925E.9020001@siemens.com>
On 09/09/2009 02:32 PM, Jan Kiszka wrote:
>
>> This (as merged into kvm-next) breaks autotest. Autotest starts
>> qemu-kvm with -monitor unix:/tmp/blah,server,nowait; with this patch it
>> no longer opens the socket (as seen with lsof). I haven't yet found out
>> why.
>>
> Ok, will have a look.
>
>
I think it's a merge error, not a but in the commit itself.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-09-09 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200909041443.n84EhZaA005101@d01av04.pok.ibm.com>
2009-09-09 11:30 ` [Qemu-devel] Re: [Qemu-commits] [COMMIT ddd9bbd] Support for multiple -monitor devices Avi Kivity
2009-09-09 11:32 ` Jan Kiszka
2009-09-09 11:42 ` Avi Kivity [this message]
2009-09-09 11:47 ` Avi Kivity
2009-09-09 11:50 ` Jan Kiszka
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=4AA794A8.30401@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--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).