From: "Zhang, Chen" <chen.zhang@intel.com>
To: Lukas Straub <lukasstraub2@web.de>, qemu-devel <qemu-devel@nongnu.org>
Cc: Jason Wang <jasowang@redhat.com>, Li Zhijian <lizhijian@cn.fujitsu.com>
Subject: RE: [PATCH 0/2] colo-compare: Fix memory leak for non-tcp packet
Date: Mon, 16 Nov 2020 07:32:22 +0000 [thread overview]
Message-ID: <2cee934e177e4a778b3bcc8d5085f4f0@intel.com> (raw)
In-Reply-To: <cover.1605438886.git.lukasstraub2@web.de>
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:[~2020-11-16 7:35 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 ` Zhang, Chen [this message]
2021-03-17 21:23 ` [PATCH 0/2] colo-compare: Fix memory leak for non-tcp packet Lukas Straub
2021-03-18 1:22 ` Zhang, Chen
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=2cee934e177e4a778b3bcc8d5085f4f0@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).