From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Haowen Bai <baihaowen@meizu.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: <linux-renesas-soc@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] clk: renesas: Fix memory leak of 'cpg'
Date: Thu, 14 Apr 2022 12:29:08 +0300 [thread overview]
Message-ID: <2ed01eb3-ff46-425c-75dc-81729a5c30a8@omp.ru> (raw)
In-Reply-To: <1649837953-10984-1-git-send-email-baihaowen@meizu.com>
Hello!
On 4/13/22 11:19 AM, Haowen Bai wrote:
> Fix this issue by freeing the cpg when exiting the function in the
> error/normal path.
>
> Signed-off-by: Haowen Bai <baihaowen@meizu.com>
> ---
> V1->V2: free both cpg&clks.
>
> drivers/clk/renesas/clk-r8a73a4.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
2 patches with the same name won't do -- you always need to include the chip name
part of the file name in the subject (in this case r8a73a4).
MBR, Sergey
next prev parent reply other threads:[~2022-04-14 9:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 8:19 [PATCH V2] clk: renesas: Fix memory leak of 'cpg' Haowen Bai
2022-04-13 8:41 ` Geert Uytterhoeven
2022-04-13 9:24 ` baihaowen
2022-04-13 10:39 ` Geert Uytterhoeven
2022-04-14 9:29 ` Sergey Shtylyov [this message]
2022-04-14 9:31 ` baihaowen
2022-04-14 9:32 ` Geert Uytterhoeven
2022-04-14 18:26 ` Sergey Shtylyov
[not found] <8dvhtgydaq7tflf8q4rq4fpu.1649846600874@email.android.com>
2022-04-13 11:23 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2022-04-13 8:16 Haowen Bai
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=2ed01eb3-ff46-425c-75dc-81729a5c30a8@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=baihaowen@meizu.com \
--cc=geert+renesas@glider.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
/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).