mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] microblaze: CCF: fix refcount leak
Date: Tue, 1 Sep 2026 14:19:41 +0200	[thread overview]
Message-ID: <8056e1f8-6257-417c-83b1-b73c2acaba56@monstr.eu> (raw)
In-Reply-To: <20260526184105.18962-4-grandmaster@al2klimov.de>



On 5/26/26 20:40, Alexander A. Klimov wrote:
> Every value returned from of_clk_get() is supposed to be cleaned up
> via clk_put() once not needed anymore.
> 
> Fixes: c1120542b99a ("microblaze: Add support for CCF")
> Signed-off-by: Alexander A. Klimov <grandmaster@al2klimov.de>
> ---
>   arch/microblaze/kernel/cpu/cpuinfo.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/arch/microblaze/kernel/cpu/cpuinfo.c b/arch/microblaze/kernel/cpu/cpuinfo.c
> index cd9b4450763b..32c508e85408 100644
> --- a/arch/microblaze/kernel/cpu/cpuinfo.c
> +++ b/arch/microblaze/kernel/cpu/cpuinfo.c
> @@ -133,6 +133,7 @@ void __init setup_cpuinfo_clk(void)
>   		cpuinfo.cpu_clock_freq = fcpu(cpu, "timebase-frequency");
>   	} else {
>   		cpuinfo.cpu_clock_freq = clk_get_rate(clk);
> +		clk_put(clk);
>   	}
>   
>   	if (!cpuinfo.cpu_clock_freq) {

Applied.
M

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP/Versal ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal/Versal NET SoCs
TF-A maintainer - Xilinx ZynqMP/Versal/Versal NET SoCs


  reply	other threads:[~2026-09-01 12:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26 18:40 [PATCH] clk: mvebu: ap-cpu-clk: " Alexander A. Klimov
2026-05-26 18:40 ` [PATCH] clocksource/drivers/clps711x: " Alexander A. Klimov
2026-05-26 18:40 ` [PATCH] clocksource/timer-econet-en751221: " Alexander A. Klimov
2026-05-28 16:05   ` Caleb James DeLisle
2026-05-26 18:40 ` [PATCH] microblaze: CCF: " Alexander A. Klimov
2026-09-01 12:19   ` Michal Simek [this message]
2026-05-26 18:41 ` [PATCH] drm/vc4: fix krealloc() memory leak Alexander A. Klimov
2026-05-28 18:17   ` Maíra Canal
2026-05-28 18:54     ` Alexander A. Klimov
2026-05-28 19:01       ` Maíra Canal
2026-05-31 19:55     ` [PATCH v2] " Alexander A. Klimov
2026-06-01  3:34       ` Joe Perches
2026-06-06 12:38         ` [PATCH v3] " Alexander A. Klimov
2026-06-06 13:32           ` Maíra Canal
2026-06-09 18:49           ` Maíra Canal
2026-05-26 18:41 ` [PATCH] ibmvnic: " Alexander A. Klimov
2026-05-26 20:50   ` Nicolai Buchwitz
2026-05-27 17:22     ` Alexander A. Klimov
2026-05-26 22:41 ` [PATCH] clk: mvebu: ap-cpu-clk: fix refcount leak Brian Masney

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=8056e1f8-6257-417c-83b1-b73c2acaba56@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=grandmaster@al2klimov.de \
    --cc=linux-kernel@vger.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®