From: "Zhang, Chen" <chen.zhang@intel.com>
To: Lukas Straub <lukasstraub2@web.de>, Jason Wang <jasowang@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Li Zhijian <lizhijian@cn.fujitsu.com>
Subject: RE: [PATCH 0/2] colo-compare: Fix memory leak for non-tcp packet
Date: Thu, 18 Mar 2021 01:22:11 +0000 [thread overview]
Message-ID: <ea3c4558ebad42c8b12210c9b1b552de@intel.com> (raw)
In-Reply-To: <20210317222358.31864ded@gecko.fritz.box>
Sorry for the delay. Current COLO tree just merged this series,
I originally wanted to merge other COLO related patches(Lei or me) and submit it together to Jason.
Hi Jason, do you need me to send this series first or do you want to do it together?
Thanks
Chen
> -----Original Message-----
> From: Lukas Straub <lukasstraub2@web.de>
> Sent: Thursday, March 18, 2021 5:24 AM
> To: Zhang, Chen <chen.zhang@intel.com>
> Cc: qemu-devel <qemu-devel@nongnu.org>; Li Zhijian
> <lizhijian@cn.fujitsu.com>; Jason Wang <jasowang@redhat.com>
> Subject: Re: [PATCH 0/2] colo-compare: Fix memory leak for non-tcp packet
>
> Hi,
> This hasn't been merged yet.
>
> Regards,
> Lukas Straub
>
> On Mon, 16 Nov 2020 07:32:22 +0000
> "Zhang, Chen" <chen.zhang@intel.com> wrote:
>
> > Queued this series to COLO tree.
> >
> > Thanks
> > Chen
> >
> > > -----Original Message-----
> > > From: Lukas Straub <lukasstraub2@web.de>
> > > Sent: Sunday, November 15, 2020 7:19 PM
> > > To: qemu-devel <qemu-devel@nongnu.org>
> > > Cc: Zhang, Chen <chen.zhang@intel.com>; Li Zhijian
> > > <lizhijian@cn.fujitsu.com>; Jason Wang <jasowang@redhat.com>
> > > Subject: [PATCH 0/2] colo-compare: Fix memory leak for non-tcp
> > > packet
> > >
> > > Hello Everyone,
> > > This fixes a memory leak for non-tcp packets and optimizes the
> > > removal from the queue.
> > >
> > > Lukas Straub (2):
> > > net/colo-compare.c: Fix memory leak for non-tcp packet
> > > net/colo-compare.c: Optimize removal of secondary packet
> > >
> > > net/colo-compare.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > --
> > > 2.20.1
>
>
>
> --
next prev parent reply other threads:[~2021-03-18 1:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 11:18 [PATCH 0/2] colo-compare: Fix memory leak for non-tcp packet Lukas Straub
2020-11-15 11:19 ` [PATCH 1/2] net/colo-compare.c: " Lukas Straub
2020-11-16 7:31 ` Zhang, Chen
2020-11-15 11:19 ` [PATCH 2/2] net/colo-compare.c: Optimize removal of secondary packet Lukas Straub
2020-11-16 7:31 ` Zhang, Chen
2020-11-16 7:32 ` [PATCH 0/2] colo-compare: Fix memory leak for non-tcp packet Zhang, Chen
2021-03-17 21:23 ` Lukas Straub
2021-03-18 1:22 ` Zhang, Chen [this message]
2021-03-18 2:41 ` Jason Wang
2021-03-18 3:26 ` 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=ea3c4558ebad42c8b12210c9b1b552de@intel.com \
--to=chen.zhang@intel.com \
--cc=jasowang@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=lukasstraub2@web.de \
--cc=qemu-devel@nongnu.org \
/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).