From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: pannengyuan@huawei.com, peter.maydell@linaro.org
Cc: zhang.zhanghailiang@huawei.com, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/3] delay timer_new to avoid memleaks
Date: Wed, 5 Feb 2020 14:16:41 +0100 [thread overview]
Message-ID: <ef35a825-b1c8-84cf-a72a-3c4877b5ad98@redhat.com> (raw)
In-Reply-To: <20200205070659.22488-1-pannengyuan@huawei.com>
On 2/5/20 8:06 AM, pannengyuan@huawei.com wrote:
> From: Pan Nengyuan <pannengyuan@huawei.com>
>
> This series delay timer_new into realize() to fix some memleaks when we call 'device-list-properties'.
>
> Pan Nengyuan (3):
> armv7m_systick: delay timer_new to avoid memleaks
> stm32f2xx_timer: delay timer_new to avoid memleaks
> stellaris: delay timer_new to avoid memleaks
>
> hw/arm/stellaris.c | 7 ++++++-
> hw/timer/armv7m_systick.c | 6 ++++++
> hw/timer/stm32f2xx_timer.c | 5 +++++
> 3 files changed, 17 insertions(+), 1 deletion(-)
You might want to look at Coccinelle [*] and write a spatch script to
check/fix all the codebase at once. You can find some examples in
scripts/coccinelle/.
[*] http://coccinelle.lip6.fr/
next prev parent reply other threads:[~2020-02-05 13:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 7:06 [PATCH 0/3] delay timer_new to avoid memleaks pannengyuan
2020-02-05 7:06 ` [PATCH 1/3] armv7m_systick: " pannengyuan
2020-02-05 7:06 ` [PATCH 2/3] stm32f2xx_timer: " pannengyuan
2020-02-05 13:17 ` Philippe Mathieu-Daudé
2020-02-05 18:49 ` Alistair Francis
2020-02-05 7:06 ` [PATCH 3/3] stellaris: " pannengyuan
2020-02-05 13:10 ` Philippe Mathieu-Daudé
2020-02-05 13:16 ` Philippe Mathieu-Daudé [this message]
2020-02-06 1:14 ` [PATCH 0/3] " Pan Nengyuan
2020-02-07 13:42 ` Peter Maydell
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=ef35a825-b1c8-84cf-a72a-3c4877b5ad98@redhat.com \
--to=philmd@redhat.com \
--cc=pannengyuan@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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).