From: Paolo Bonzini <pbonzini@redhat.com>
To: "Max Reitz" <mreitz@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Alberto Garcia" <berto@igalia.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/3] char-socket: Fix race condition
Date: Thu, 4 Jul 2019 11:59:17 +0200 [thread overview]
Message-ID: <f1d226f3-f80e-f764-01a7-c18fa79d2248@redhat.com> (raw)
In-Reply-To: <1c1c3302-a87c-6e3e-d1d7-c805972a7384@redhat.com>
On 03/07/19 19:51, Max Reitz wrote:
> On 05.06.19 21:36, Max Reitz wrote:
>> On 26.04.19 09:51, Paolo Bonzini wrote:
>>> On 23/04/19 18:55, Daniel P. Berrangé wrote:
>>>> ping - paolo/marc-andré - unless I'm missing something, it looks like
>>>> this chardev series slipped through the cracks and missed 4.0
>>>
>>> Yeah, it had a bug unfortunately. I'm looking at it RSN.
>>
>> I’ll just leave another ping here
I haven't forgotten. :(
Paolo
next prev parent reply other threads:[~2019-07-04 10:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 13:46 [Qemu-devel] [PATCH v3 0/3] char-socket: Fix race condition Alberto Garcia
2019-02-22 13:46 ` [Qemu-devel] [PATCH v3 1/3] main-loop: Fix GSource leak in qio_task_thread_worker() Alberto Garcia
2019-02-22 13:46 ` [Qemu-devel] [PATCH v3 2/3] main-loop: Add qemu_idle_add() Alberto Garcia
2019-02-22 13:46 ` [Qemu-devel] [PATCH v3 3/3] char-socket: Lock tcp_chr_disconnect() and socket_reconnect_timeout() Alberto Garcia
2019-02-22 13:51 ` Daniel P. Berrangé
2019-07-16 9:56 ` Max Reitz
2019-03-05 15:52 ` [Qemu-devel] [PATCH v3 0/3] char-socket: Fix race condition Alberto Garcia
2019-03-05 15:55 ` Marc-André Lureau
2019-03-06 10:58 ` Paolo Bonzini
2019-04-23 16:55 ` Daniel P. Berrangé
2019-04-23 16:55 ` Daniel P. Berrangé
2019-04-26 7:51 ` Paolo Bonzini
2019-04-26 7:51 ` Paolo Bonzini
2019-06-05 19:36 ` Max Reitz
2019-07-03 17:51 ` Max Reitz
2019-07-04 9:59 ` Paolo Bonzini [this message]
2019-07-16 12:55 ` Andrey Shinkevich
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=f1d226f3-f80e-f764-01a7-c18fa79d2248@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=berto@igalia.com \
--cc=marcandre.lureau@redhat.com \
--cc=mreitz@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).