From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Haowen Bai <baihaowen@meizu.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] clk: renesas: Fix memory leak of 'cpg'
Date: Thu, 14 Apr 2022 21:26:39 +0300 [thread overview]
Message-ID: <ad8972c2-5261-406a-c98e-d8c3d382fc7d@omp.ru> (raw)
In-Reply-To: <CAMuHMdVCRRbhYEnk4bjvPugrosw4mNQCcHQqsNrx0RhFL+dJDQ@mail.gmail.com>
On 4/14/22 12:32 PM, Geert Uytterhoeven 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).
>
> Oh, they were for multiple drivers?
I counted 3! :-)
> I hadn't even noticed , as Gmail collapsed them all into the same thread...
Hm, they weren't actually posted in the same thread...
> Gr{oetje,eeting}s,
>
> Geert
[...]
MBR, Sergey
next prev parent reply other threads:[~2022-04-14 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 8:19 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
2022-04-14 9:31 ` baihaowen
2022-04-14 9:32 ` Geert Uytterhoeven
2022-04-14 18:26 ` Sergey Shtylyov [this message]
[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=ad8972c2-5261-406a-c98e-d8c3d382fc7d@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=baihaowen@meizu.com \
--cc=geert@linux-m68k.org \
--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
all inboxes | Powered by JetHome®