From: Pan Nengyuan <pannengyuan@huawei.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.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: Thu, 6 Feb 2020 09:14:51 +0800 [thread overview]
Message-ID: <f21be513-ed77-8a9d-f033-ad22c940c382@huawei.com> (raw)
In-Reply-To: <ef35a825-b1c8-84cf-a72a-3c4877b5ad98@redhat.com>
On 2/5/2020 9:16 PM, Philippe Mathieu-Daudé wrote:
> 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/.
Thanks for these tips. I will pay attention.
>
> [*] http://coccinelle.lip6.fr/
>
next prev parent reply other threads:[~2020-02-06 1:16 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 ` [PATCH 0/3] " Philippe Mathieu-Daudé
2020-02-06 1:14 ` Pan Nengyuan [this message]
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=f21be513-ed77-8a9d-f033-ad22c940c382@huawei.com \
--to=pannengyuan@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--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 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.