From: "Zhang, Chen" <chen.zhang@intel.com>
To: Jason Wang <jasowang@redhat.com>, qemu-dev <qemu-devel@nongnu.org>
Cc: Zhang Chen <zhangckid@gmail.com>
Subject: RE: [PATCH 0/2] net/colo-compare.c: Expose "max_queue_size" to users and clean up
Date: Thu, 23 Apr 2020 08:59:11 +0000 [thread overview]
Message-ID: <310162af410e43ea9e0d0a22012e1929@intel.com> (raw)
In-Reply-To: <18466058-4184-2c6e-d740-2a1479395506@redhat.com>
> -----Original Message-----
> From: Jason Wang <jasowang@redhat.com>
> Sent: Thursday, April 23, 2020 4:54 PM
> To: Zhang, Chen <chen.zhang@intel.com>; qemu-dev <qemu-
> devel@nongnu.org>
> Cc: Zhang Chen <zhangckid@gmail.com>
> Subject: Re: [PATCH 0/2] net/colo-compare.c: Expose "max_queue_size" to
> users and clean up
>
>
> On 2020/4/23 下午3:31, Zhang, Chen wrote:
> > Hi Jason,
> >
> > Please review this series when you free.
> >
> > Thanks
> > Zhang Chen
> >
>
> Sure.
>
> I wonder maybe it's better e.g you can review and collect the patches that
> looks good and send them to me periodically?
OK, I will queue COLO related patch as one series to you.
Do I need send a pull request? or just a big patch set?
Thanks
Zhang Chen
>
> Thanks
next prev parent reply other threads:[~2020-04-23 9:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 3:38 [PATCH 0/2] net/colo-compare.c: Expose "max_queue_size" to users and clean up Zhang Chen
2020-04-11 3:38 ` [PATCH 1/2] net/colo-compare.c: Expose compare "max_queue_size" to users Zhang Chen
2020-04-11 3:38 ` [PATCH 2/2] qemu-options.hx: Clean up and fix typo for colo-compare Zhang Chen
2020-04-23 7:31 ` [PATCH 0/2] net/colo-compare.c: Expose "max_queue_size" to users and clean up Zhang, Chen
2020-04-23 8:54 ` Jason Wang
2020-04-23 8:59 ` Zhang, Chen [this message]
2020-04-23 9:07 ` Jason Wang
2020-04-24 1:26 ` Zhang, Chen
2020-04-24 2:19 ` Jason Wang
2020-06-19 17:46 ` Lukas Straub
2020-06-23 1:47 ` Zhang, Chen
2020-06-23 5:53 ` Jason Wang
2020-06-24 3:13 ` 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=310162af410e43ea9e0d0a22012e1929@intel.com \
--to=chen.zhang@intel.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 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.