From: AlexChen <alex.chen@huawei.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Michael Tokarev" <mjt@tls.msk.ru>,
"Laurent Vivier" <laurent@vivier.eu>
Cc: QEMU <qemu-devel@nongnu.org>,
QEMU Trivial <qemu-trivial@nongnu.org>,
<zhang.zhanghailiang@huawei.com>
Subject: [PATCH V2 0/2] plugins: Fix some resource leaks
Date: Fri, 6 Nov 2020 09:59:39 +0800 [thread overview]
Message-ID: <5FA4AE0B.1000007@huawei.com> (raw)
There are 3 resource leaks in contrib/plugins/lockstep.c, fix it.
v1->v2:
- add the cover letter
- modify the subject of the patch[2/2]
alexchen (2):
plugins: Fix resource leak in connect_socket()
plugins: Fix two resource leaks in setup_socket()
contrib/plugins/lockstep.c | 3 +++
1 file changed, 3 insertions(+)
--
2.19.1
WARNING: multiple messages have this Message-ID (diff)
From: AlexChen <alex.chen@huawei.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Michael Tokarev" <mjt@tls.msk.ru>,
"Laurent Vivier" <laurent@vivier.eu>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
QEMU <qemu-devel@nongnu.org>,
zhang.zhanghailiang@huawei.com
Subject: [PATCH V2 0/2] plugins: Fix some resource leaks
Date: Fri, 6 Nov 2020 09:59:39 +0800 [thread overview]
Message-ID: <5FA4AE0B.1000007@huawei.com> (raw)
There are 3 resource leaks in contrib/plugins/lockstep.c, fix it.
v1->v2:
- add the cover letter
- modify the subject of the patch[2/2]
alexchen (2):
plugins: Fix resource leak in connect_socket()
plugins: Fix two resource leaks in setup_socket()
contrib/plugins/lockstep.c | 3 +++
1 file changed, 3 insertions(+)
--
2.19.1
next reply other threads:[~2020-11-06 2:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 1:59 AlexChen [this message]
2020-11-06 1:59 ` [PATCH V2 0/2] plugins: Fix some resource leaks AlexChen
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=5FA4AE0B.1000007@huawei.com \
--to=alex.chen@huawei.com \
--cc=alex.bennee@linaro.org \
--cc=laurent@vivier.eu \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=zhang.zhanghailiang@huawei.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.