From: "Zhang, Chen" <chen.zhang@intel.com>
To: Jason Wang <jasowang@redhat.com>, Lukas Straub <lukasstraub2@web.de>
Cc: qemu-dev <qemu-devel@nongnu.org>, Zhang Chen <zhangckid@gmail.com>
Subject: RE: [PATCH 0/2] net/colo-compare.c: Expose "max_queue_size" to users and clean up
Date: Wed, 24 Jun 2020 03:13:51 +0000 [thread overview]
Message-ID: <ad352186b43349f08b93ffa8ffbff525@intel.com> (raw)
In-Reply-To: <cb77d0c2-f3ee-2ba9-e495-3fc325eb122c@redhat.com>
> -----Original Message-----
> From: Jason Wang <jasowang@redhat.com>
> Sent: Tuesday, June 23, 2020 1:54 PM
> To: Zhang, Chen <chen.zhang@intel.com>; Lukas Straub
> <lukasstraub2@web.de>
> Cc: qemu-dev <qemu-devel@nongnu.org>; 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/6/23 上午9:47, Zhang, Chen wrote:
> >
> >> -----Original Message-----
> >> From: Lukas Straub <lukasstraub2@web.de>
> >> Sent: Saturday, June 20, 2020 1:47 AM
> >> To: Jason Wang <jasowang@redhat.com>
> >> Cc: Zhang, Chen <chen.zhang@intel.com>; qemu-dev <qemu-
> >> devel@nongnu.org>; Zhang Chen <zhangckid@gmail.com>
> >> Subject: Re: [PATCH 0/2] net/colo-compare.c: Expose "max_queue_size"
> >> to users and clean up
> >>
> >> On Fri, 24 Apr 2020 10:19:48 +0800
> >> Jason Wang <jasowang@redhat.com> wrote:
> >>
> >>> On 2020/4/11 上午11:38, Zhang Chen wrote:
> >>>> From: Zhang Chen <chen.zhang@intel.com>
> >>>>
> >>>> This series make a way to config COLO "max_queue_size" parameters
> >>>> according to user's scenarios and environments and do some clean up
> >>>> for
> >> descriptions.
> >>>> Zhang Chen (2):
> >>>> net/colo-compare.c: Expose compare "max_queue_size" to users
> >>>> qemu-options.hx: Clean up and fix typo for colo-compare
> >>>>
> >>>> net/colo-compare.c | 43
> >> ++++++++++++++++++++++++++++++++++++++++++-
> >>>> qemu-options.hx | 33 +++++++++++++++++----------------
> >>>> 2 files changed, 59 insertions(+), 17 deletions(-)
> >>>
> >>> Queued for 5.1.
> >>>
> >>> Thanks
> >>>
> >>>
> >> Hi,
> >> It looks like this hasn't been merged.
> > Thanks Lukas.
> > Hi Jason, I have double checked on upstream, looks missed this series.
> >
> > Thanks
> > Zhang Chen
>
>
> Right, but unfortunately it can't be applied cleanly on master.
>
> Please send a new version.
>
> Sorry.
It's OK, I have send V2 version of this series, please merge it.
Thanks
Zhang Chen
>
> Thanks
>
>
> >
> >> Regards,
> >> Lukas Straub
prev parent reply other threads:[~2020-06-24 3:14 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
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 [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=ad352186b43349f08b93ffa8ffbff525@intel.com \
--to=chen.zhang@intel.com \
--cc=jasowang@redhat.com \
--cc=lukasstraub2@web.de \
--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).