From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Li Zhijian <lizhijian@cn.fujitsu.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
eddie dong <eddie.dong@intel.com>,
Yang Hongyang <imhy.yang@gmail.com>,
Xen devel <xen-devel@lists.xenproject.org>,
Bian Naimeng <biannm@cn.fujitsu.com>
Subject: Re: [PATCH V4 0/8] COLO-Proxy: Make Xen COLO use userspace colo-proxy
Date: Mon, 6 Mar 2017 09:31:36 -0500 [thread overview]
Message-ID: <20170306143136.GG27211@char.us.oracle.com> (raw)
In-Reply-To: <1488769166-28738-1-git-send-email-zhangchen.fnst@cn.fujitsu.com>
On Mon, Mar 06, 2017 at 10:59:18AM +0800, Zhang Chen wrote:
> Because of some reason, We no longer support COLO kernel proxy.
However the #7 talks about kernel colo proxy? Is this description
out-dated?
> V4:
One usually adds these comments to the patches. That is
right after the '---' you say:
v4: New patch
(for the new patches)
Or for the older patches (like #7):
v4: Fix typo.
Fix 'some bug' (perhaps be specific).
> - Because the origin 3/7 has been merged,
> remove it in this series.
> - Add new patch "COLO-Proxy: Add colo-compare notify args"
> to support qemu side patch:
> https://lists.nongnu.org/archive/html/qemu-devel/2017-02/msg07265.html
>
> - Add colo_userspace_proxy macro as a separate patch.
> - Add some comments about COLO and fix some typo in patch 2/7.
> - Fix some bug and typo in patch 7/7.
But the subject is 0/8? So it can't be 7/7. Did you mean
7/8? or 8/8/?
> - Rebase codes on upstream Xen.
Thanks!
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-06 14:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 2:59 [PATCH V4 0/8] COLO-Proxy: Make Xen COLO use userspace colo-proxy Zhang Chen
2017-03-06 2:59 ` [PATCH V4 1/8] COLO-Proxy: Add remus command to open userspace proxy Zhang Chen
2017-03-14 11:23 ` Wei Liu
2017-03-06 2:59 ` [PATCH V4 2/8] COLO-Proxy: Setup userspace colo-proxy on primary side Zhang Chen
2017-03-14 11:24 ` Wei Liu
2017-03-06 2:59 ` [PATCH V4 3/8] COLO-Proxy: Setup userspace colo-proxy on secondary side Zhang Chen
2017-03-14 11:24 ` Wei Liu
2017-03-06 2:59 ` [PATCH V4 4/8] COLO-Proxy: Add primary userspace colo proxy start args Zhang Chen
2017-03-14 11:24 ` Wei Liu
2017-03-06 2:59 ` [PATCH V4 5/8] COLO-Proxy: Add secondary userspace colo-proxy " Zhang Chen
2017-03-14 11:24 ` Wei Liu
2017-03-14 11:39 ` Wei Liu
2017-03-15 1:53 ` Zhang Chen
2017-03-06 2:59 ` [PATCH V4 6/8] COLO-Proxy: Add colo-compare notify args Zhang Chen
2017-03-14 11:24 ` Wei Liu
2017-03-06 2:59 ` [PATCH V4 7/8] COLO-Proxy: Use socket to get checkpoint event Zhang Chen
2017-03-14 11:24 ` Wei Liu
2017-03-15 2:02 ` Zhang Chen
2017-03-15 10:56 ` Wei Liu
2017-03-16 1:21 ` Zhang Chen
2017-03-06 2:59 ` [PATCH V4 8/8] COLO-proxy: Add colo_userspace_proxy macro Zhang Chen
2017-03-14 11:24 ` Wei Liu
2017-03-06 14:31 ` Konrad Rzeszutek Wilk [this message]
2017-03-07 3:25 ` [PATCH V4 0/8] COLO-Proxy: Make Xen COLO use userspace colo-proxy Zhang Chen
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=20170306143136.GG27211@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=biannm@cn.fujitsu.com \
--cc=eddie.dong@intel.com \
--cc=imhy.yang@gmail.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
--cc=zhangchen.fnst@cn.fujitsu.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).