From: Jason Wang <jasowang@redhat.com>
To: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
qemu devel <qemu-devel@nongnu.org>
Cc: Li Zhijian <lizhijian@cn.fujitsu.com>,
"eddie . dong" <eddie.dong@intel.com>,
bian naimeng <biannm@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH 1/3] COLO-compare: Add packet size check and some fix
Date: Tue, 28 Feb 2017 11:22:02 +0800 [thread overview]
Message-ID: <62068d09-fce2-c621-8bbb-ab9844a095af@redhat.com> (raw)
In-Reply-To: <1904fbc3-61f5-b414-6926-c18d4e9b90a2@cn.fujitsu.com>
On 2017年02月25日 11:43, Zhang Chen wrote:
> Sorry, This patch has been renamed.
>
> please ignore this patch.
>
>
> Thanks
>
> Zhang Chen
Want to repost to just withdraw this series (patch 2 does not apply)?
Thanks
next prev parent reply other threads:[~2017-02-28 3:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 3:32 [Qemu-devel] [PATCH 0/3] COLO-compare: Optimize the code and fix some bug Zhang Chen
2017-02-25 3:32 ` [Qemu-devel] [PATCH 1/3] COLO-compare: Add minimum packet size check and some fix Zhang Chen
2017-02-25 6:43 ` Hailiang Zhang
2017-02-27 6:39 ` Zhang Chen
2017-02-25 3:32 ` [Qemu-devel] [PATCH 1/3] COLO-compare: Add " Zhang Chen
2017-02-25 3:43 ` Zhang Chen
2017-02-28 3:22 ` Jason Wang [this message]
2017-02-28 3:27 ` Zhang Chen
2017-02-25 3:32 ` [Qemu-devel] [PATCH 2/3] COLO-compare: Optimize colo_packet_compare_common Zhang Chen
2017-02-25 6:58 ` Hailiang Zhang
2017-02-27 7:03 ` Zhang Chen
2017-02-27 7:28 ` Hailiang Zhang
2017-02-27 7:34 ` Zhang Chen
2017-02-27 8:43 ` Hailiang Zhang
2017-02-27 9:02 ` Zhang Chen
2017-02-25 7:26 ` Hailiang Zhang
2017-02-27 7:06 ` Zhang Chen
2017-02-25 3:32 ` [Qemu-devel] [PATCH 3/3] COLO-compare: Make qemu_hexdump() print data when trace-event ON 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=62068d09-fce2-c621-8bbb-ab9844a095af@redhat.com \
--to=jasowang@redhat.com \
--cc=biannm@cn.fujitsu.com \
--cc=eddie.dong@intel.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=qemu-devel@nongnu.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).