From: "Zhang, Chen" <chen.zhang@intel.com>
To: Jason Wang <jasowang@redhat.com>, qemu-dev <qemu-devel@nongnu.org>
Cc: Daniel Cho <danielcho@qnap.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Zhang Chen <zhangckid@gmail.com>
Subject: RE: [PATCH 0/2] net/colo-compare.c: Expose more COLO internal
Date: Wed, 18 Mar 2020 07:00:32 +0000 [thread overview]
Message-ID: <c3bd15a84ae44a479b6a9d179740546c@intel.com> (raw)
In-Reply-To: <6f05b6a2-cd63-e0a0-f24e-f99a2f1a9f02@redhat.com>
> -----Original Message-----
> From: Jason Wang <jasowang@redhat.com>
> Sent: Wednesday, March 18, 2020 10:48 AM
> To: Zhang, Chen <chen.zhang@intel.com>; qemu-dev <qemu-
> devel@nongnu.org>
> Cc: Daniel Cho <danielcho@qnap.com>; Dr . David Alan Gilbert
> <dgilbert@redhat.com>; Zhang Chen <zhangckid@gmail.com>
> Subject: Re: [PATCH 0/2] net/colo-compare.c: Expose more COLO internal
>
>
> On 2020/3/17 下午4:25, Zhang, Chen wrote:
> > Hi Jason,
> >
> > No news for a while.
> > Please review this series when you have time.
> >
> > Thanks
> > Zhang Chen
>
>
> Sorry for the delay.
>
> Patch looks good to me.
>
> But it can not be applied cleanly on master.
>
> Please rebase and send V2 (btw, I notice some typos in the commit log,
> please try to fix them as well).
Sure.
Thanks
Zhang Chen
>
> Thanks
prev parent reply other threads:[~2020-03-18 7:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 20:58 [PATCH 0/2] net/colo-compare.c: Expose more COLO internal Zhang Chen
2020-02-23 20:58 ` [PATCH 1/2] net/colo-compare.c: Expose "compare_timeout" to user Zhang Chen
2020-02-23 20:58 ` [PATCH 2/2] net/colo-compare.c: Expose "expired_scan_cycle" " Zhang Chen
2020-03-04 7:59 ` [PATCH 0/2] net/colo-compare.c: Expose more COLO internal Zhang, Chen
2020-03-17 8:25 ` Zhang, Chen
2020-03-18 2:47 ` Jason Wang
2020-03-18 7:00 ` Zhang, Chen [this message]
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=c3bd15a84ae44a479b6a9d179740546c@intel.com \
--to=chen.zhang@intel.com \
--cc=danielcho@qnap.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhangckid@gmail.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 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).