From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, Emilio G Cota <cota@braap.org>
Subject: Re: [Qemu-devel] [PATCH] vl: Fix broken thread=xxx option of the --accel parameter
Date: Thu, 8 Jun 2017 14:56:02 +0200 [thread overview]
Message-ID: <4339634c-00d0-0bfd-8da7-6013c759da82@redhat.com> (raw)
In-Reply-To: <424f8720-7bf6-33b1-f6a5-a8ed3494a648@redhat.com>
On 08.06.2017 14:53, Paolo Bonzini wrote:
>
>
> On 08/06/2017 09:04, Markus Armbruster wrote:
>> The fix is fine, so
>>
>> Reviewed-by: Markus Armbruster <armbru@redhat.com>
>
> Who's going to merge it?
Could you do it, Paolo? You also merged my commit bde4d9205 that
introduced this bug...
Thomas
next prev parent reply other threads:[~2017-06-08 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 5:20 [Qemu-devel] [PATCH] vl: Fix broken thread=xxx option of the --accel parameter Thomas Huth
2017-06-08 7:04 ` Markus Armbruster
2017-06-08 12:53 ` Paolo Bonzini
2017-06-08 12:56 ` Thomas Huth [this message]
2017-06-08 9:21 ` Alex Bennée
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=4339634c-00d0-0bfd-8da7-6013c759da82@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=cota@braap.org \
--cc=pbonzini@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).