From: <pannengyuan@huawei.com>
To: <balrogg@gmail.com>, <peter.maydell@linaro.org>,
<mav2-rk.cave-ayland@ilande.co.uk>, <david@gibson.dropbear.id.au>,
<edgar.iglesias@gmail.com>, <alistair@alistair23.me>
Cc: zhang.zhanghailiang@huawei.com,
Pan Nengyuan <pannengyuan@huawei.com>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org, qemu-ppc@nongnu.org,
euler.robot@huawei.com
Subject: [PATCH v2 0/2] delay timer_new from init to realize to fix memleaks.
Date: Mon, 17 Feb 2020 11:21:25 +0800 [thread overview]
Message-ID: <20200217032127.46508-1-pannengyuan@huawei.com> (raw)
From: Pan Nengyuan <pannengyuan@huawei.com>
v1:
- Delay timer_new() from init() to realize() to fix memleaks.
v2:
- Similarly to other cleanups, move timer_new into realize in target/s390x/cpu.c (Suggested by Philippe Mathieu-Daudé).
- Send these two patches as a series instead of sending each as a single patch but with wrong subject in v1.
Pan Nengyuan (2):
s390x: fix memleaks in cpu_finalize
hw: move timer_new from init() into realize() to avoid memleaks
hw/arm/pxa2xx.c | 17 +++++++++++------
hw/arm/spitz.c | 8 +++++++-
hw/arm/strongarm.c | 18 ++++++++++++------
hw/misc/mos6522.c | 14 ++++++++++++--
hw/timer/cadence_ttc.c | 16 +++++++++++-----
target/s390x/cpu.c | 22 ++++++++++++++++++----
6 files changed, 71 insertions(+), 24 deletions(-)
--
2.21.0.windows.1
next reply other threads:[~2020-02-17 3:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 3:21 pannengyuan [this message]
2020-02-17 3:21 ` [PATCH v2 1/2] s390x: fix memleaks in cpu_finalize pannengyuan
2020-02-17 9:45 ` Philippe Mathieu-Daudé
2020-02-20 15:59 ` Cornelia Huck
2020-02-20 16:49 ` Peter Maydell
2020-02-17 3:21 ` [PATCH v2 2/2] hw: move timer_new from init() into realize() to avoid memleaks pannengyuan
2020-02-20 17:56 ` Peter Maydell
2020-02-20 18:51 ` Philippe Mathieu-Daudé
2020-02-20 21:20 ` Peter Maydell
2020-02-21 3:37 ` Pan Nengyuan
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=20200217032127.46508-1-pannengyuan@huawei.com \
--to=pannengyuan@huawei.com \
--cc=alistair@alistair23.me \
--cc=balrogg@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=edgar.iglesias@gmail.com \
--cc=euler.robot@huawei.com \
--cc=mav2-rk.cave-ayland@ilande.co.uk \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 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).