From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/3] Remove the obsolete non-blocking connect
Date: Wed, 14 Sep 2016 09:42:28 +0800 [thread overview]
Message-ID: <57D8AB04.1060604@cn.fujitsu.com> (raw)
In-Reply-To: <7047097c-a969-98b0-7a9e-afa714b870d4@redhat.com>
Hi Paolo,
patch 1 seems conflicts with upstream when I rebase(conflicts with
616018352, but very tiny). and patch 2 isn't in your pull request. Do
you want me to resend these two?
On 08/01/2016 06:08 PM, Paolo Bonzini wrote:
>
>
> On 28/07/2016 11:03, Cao jin wrote:
>> forget to cc maintainers in cover-letter..
>
> Patches 1 and 2 look good, thanks!
>
>> On 07/28/2016 04:54 PM, Cao jin wrote:
>>> v2 changelog:
>>> 1. revert the yoda-condition in patch 2 (Daniel)
>>>
>>> Cao jin (3):
>>> util: remove the obsolete non-blocking connect
>>> util: fix some coding style issue
>>> migration/socket: fix typo in file header
>>>
>>> include/qemu/sockets.h | 7 +-
>>> io/channel-socket.c | 2 +-
>>> migration/socket.c | 4 +-
>>> net/socket.c | 2 +-
>>> util/qemu-sockets.c | 179
>>> ++++++++-----------------------------------------
>>> 5 files changed, 33 insertions(+), 161 deletions(-)
>>>
>>
>
>
>
--
Yours Sincerely,
Cao jin
next prev parent reply other threads:[~2016-09-14 1:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 8:54 [Qemu-devel] [PATCH v2 0/3] Remove the obsolete non-blocking connect Cao jin
2016-07-28 8:54 ` [Qemu-devel] [PATCH v2 1/3] util: remove " Cao jin
2016-07-28 8:54 ` [Qemu-devel] [PATCH v2 2/3] util: fix some coding style issue Cao jin
2016-07-28 8:54 ` [Qemu-devel] [PATCH v2 3/3] migration/socket: fix typo in file header Cao jin
2016-07-28 9:03 ` [Qemu-devel] [PATCH v2 0/3] Remove the obsolete non-blocking connect Cao jin
2016-08-01 10:08 ` Paolo Bonzini
2016-09-14 1:42 ` Cao jin [this message]
2016-09-14 10:32 ` Paolo Bonzini
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=57D8AB04.1060604@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--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 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.