From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Yangtao Li <tiny.windzz@gmail.com>
Cc: mturquette@baylibre.com, sboyd@kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: kirkwood: fix refcount leak in kirkwood_clk_init()
Date: Wed, 26 Dec 2018 16:44:46 +0100 [thread overview]
Message-ID: <87y38c9tsh.fsf@bootlin.com> (raw)
In-Reply-To: <20181226134019.5229-1-tiny.windzz@gmail.com> (Yangtao Li's message of "Wed, 26 Dec 2018 08:40:19 -0500")
Hi Yangtao,
On mer., déc. 26 2018, Yangtao Li <tiny.windzz@gmail.com> wrote:
> The of_find_compatible_node() returns a node pointer with refcount
> incremented, but there is the lack of use of the of_node_put() when
> done. Add the missing of_node_put() to release the refcount.
Reviewed-by: Gregory CLEMENT <gregory.clement@bootlin.com>
Thanks,
Gregory
>
> Signed-off-by: Yangtao Li <tiny.windzz@gmail.com>
> ---
> drivers/clk/mvebu/kirkwood.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/clk/mvebu/kirkwood.c b/drivers/clk/mvebu/kirkwood.c
> index 6f784167bda4..35af3aa18f1c 100644
> --- a/drivers/clk/mvebu/kirkwood.c
> +++ b/drivers/clk/mvebu/kirkwood.c
> @@ -331,6 +331,8 @@ static void __init kirkwood_clk_init(struct device_node *np)
> if (cgnp) {
> mvebu_clk_gating_setup(cgnp, kirkwood_gating_desc);
> kirkwood_clk_muxing_setup(cgnp, kirkwood_mux_desc);
> +
> + of_node_put(cgnp);
> }
> }
> CLK_OF_DECLARE(kirkwood_clk, "marvell,kirkwood-core-clock",
> --
> 2.17.0
>
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-12-26 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 13:40 [PATCH] clk: kirkwood: fix refcount leak in kirkwood_clk_init() Yangtao Li
2018-12-26 15:44 ` Gregory CLEMENT [this message]
2018-12-28 19:46 ` Stephen Boyd
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=87y38c9tsh.fsf@bootlin.com \
--to=gregory.clement@bootlin.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=tiny.windzz@gmail.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