From: ganqixin <ganqixin@huawei.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
"Chenqun \(kuhn\)" <kuhn.chenqun@huawei.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Zhanghailiang <zhang.zhanghailiang@huawei.com>
Subject: RE: [PATCH v2 0/7] Fix some memleaks caused by ptimer_init
Date: Mon, 11 Jan 2021 02:25:39 +0000 [thread overview]
Message-ID: <A5B86EC83C48EF4CB2BC58BEF3A2F49606625057@DGGEMI525-MBS.china.huawei.com> (raw)
In-Reply-To: <CAFEAcA9Z9VDTW5GSC=R_NYF_FOoKMXQcCy3U6pctmj0jg=0-Fg@mail.gmail.com>
> -----Original Message-----
> From: Peter Maydell [mailto:peter.maydell@linaro.org]
> Sent: Friday, January 8, 2021 7:43 PM
> To: ganqixin <ganqixin@huawei.com>
> Cc: QEMU Developers <qemu-devel@nongnu.org>; QEMU Trivial
> <qemu-trivial@nongnu.org>; Beniamino Galvani <b.galvani@gmail.com>;
> Antony Pavlov <antonynpavlov@gmail.com>; Igor Mitsyanko
> <i.mitsyanko@gmail.com>; sundeep subbaraya <sundeep.lkml@gmail.com>;
> Jan Kiszka <jan.kiszka@web.de>; Chenqun (kuhn)
> <kuhn.chenqun@huawei.com>; Zhanghailiang
> <zhang.zhanghailiang@huawei.com>
> Subject: Re: [PATCH v2 0/7] Fix some memleaks caused by ptimer_init
>
> On Thu, 17 Dec 2020 at 11:32, Gan Qixin <ganqixin@huawei.com> wrote:
> >
> > v1->v2:
> > Changes suggested by Peter Maydell:
> > Delete the modification of unrelated whitespace.
> >
> > Gan Qixin (7):
> > allwinner-a10-pit: Use ptimer_free() in the finalize function to avoid
> > memleaks
> > digic-timer: Use ptimer_free() in the finalize function to avoid
> > memleaks
> > exynos4210_mct: Use ptimer_free() in the finalize function to avoid
> > memleaks
> > exynos4210_pwm: Use ptimer_free() in the finalize function to avoid
> > memleaks
> > exynos4210_rtc: Use ptimer_free() in the finalize function to avoid
> > memleaks
> > mss-timer: Use ptimer_free() in the finalize function to avoid
> > memleaks
> > musicpal: Use ptimer_free() in the finalize function to avoid
> > memleaks
>
> Applied to target-arm.next, thanks.
>
> PS: something odd happened with the threading of this series -- the patch
> emails weren't follow-ups to the cover letter -- so the automated tools like
> patchew got confused and thought the series was empty:
> https://patchew.org/QEMU/20201217113137.121607-1-ganqixin@huawei.co
> m/
>
> You might want to look into fixing that for next time you send a patchset.
>
Thanks for telling me the error that occurred when receiving this patch email. I will fix it.
prev parent reply other threads:[~2021-01-11 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 11:31 [PATCH v2 0/7] Fix some memleaks caused by ptimer_init Gan Qixin
2021-01-08 11:42 ` Peter Maydell
2021-01-11 2:25 ` ganqixin [this message]
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=A5B86EC83C48EF4CB2BC58BEF3A2F49606625057@DGGEMI525-MBS.china.huawei.com \
--to=ganqixin@huawei.com \
--cc=kuhn.chenqun@huawei.com \
--cc=peter.maydell@linaro.org \
--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 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).