From: Eric Blake <eblake@redhat.com>
To: linzhecheng <linzhecheng@huawei.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: QEMU <qemu-devel@nongnu.org>, Paolo Bonzini <pbonzini@redhat.com>,
"wangxin (U)" <wangxinxin.wang@huawei.com>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>,
"peterx@redhat.com" <peterx@redhat.com>,
"berrange@redhat.com" <berrange@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] socket: dont't free msgfds if error equals EAGAIN
Date: Tue, 29 May 2018 14:33:22 -0500 [thread overview]
Message-ID: <e4a72796-562e-adf8-21ba-7bed953126e8@redhat.com> (raw)
In-Reply-To: <D9DE8DBB19F2A24080482022C1DE758302C89900@dggemm509-mbx.china.huawei.com>
On 05/29/2018 04:33 AM, linzhecheng wrote:
> I think this patch doesn't fix my issue. For more details, please see Gonglei's reply.
> https://lists.gnu.org/archive/html/qemu-devel/2018-05/msg06296.html
Your mailer is not honoring threading (it failed to include
'In-Reply-To:' and 'References:' headers that refer to the message you
are replying to), and you are top-posting, both of which make it
difficult to follow your comments on a technical list.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-05-29 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 9:33 [Qemu-devel] [PATCH] socket: dont't free msgfds if error equals EAGAIN linzhecheng
2018-05-29 19:33 ` Eric Blake [this message]
2018-05-30 9:05 ` Gonglei (Arei)
-- strict thread matches above, loose matches on Subject: below --
2018-05-29 8:20 linzhecheng
2018-05-29 8:41 ` Gonglei (Arei)
2018-05-29 2:52 linzhecheng
2018-05-29 9:11 ` Marc-André Lureau
2018-05-30 2:56 ` Peter Xu
2018-06-01 11:46 ` Daniel P. Berrangé
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=e4a72796-562e-adf8-21ba-7bed953126e8@redhat.com \
--to=eblake@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=berrange@redhat.com \
--cc=linzhecheng@huawei.com \
--cc=marcandre.lureau@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wangxinxin.wang@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.