From: emilio@elopez.com.ar (Emilio López)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHV2]Fixes memory leak in clk-sunxi.c
Date: Sat, 14 Jun 2014 22:31:40 -0300 [thread overview]
Message-ID: <539CF77C.4010500@elopez.com.ar> (raw)
In-Reply-To: <1402794944-3357-1-git-send-email-xerofoify@gmail.com>
Hi,
El 14/06/14 22:15, Nick escribi?:
> Signed-off-by: Nick <xerofoify@gmail.com>
> ---
> drivers/clk/sunxi/clk-sunxi.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/clk/sunxi/clk-sunxi.c b/drivers/clk/sunxi/clk-sunxi.c
> index 6f4fc51..c2ce538 100644
> --- a/drivers/clk/sunxi/clk-sunxi.c
> +++ b/drivers/clk/sunxi/clk-sunxi.c
> @@ -41,10 +41,10 @@ static void __init sun4i_osc_clk_setup(struct device_node *node)
> const char *clk_name = node->name;
> u32 rate;
>
> - if (of_property_read_u32(node, "clock-frequency", &rate))
> + if (of_property_read_u32(node, "clock-frequency", &rate)) {
> kree(gate);
> return;
> -
> + }
> /* allocate fixed-rate and gate clock structs */
> fixed = kzalloc(sizeof(struct clk_fixed_rate), GFP_KERNEL);
> if (!fixed)
>
There is no memory leak there, and I think the message was pretty clear
when I mentioned it[1] and then Sergei mentioned it[2] twice[3]. As for
the bug report[4] you linked in a private email, it has been closed as
resolved by the original reporter.
Cheers,
Emilio
[1]
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/263631.html
[2]
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/263677.html
[3]
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/263683.html
[4] https://bugzilla.kernel.org/show_bug.cgi?id=59961
WARNING: multiple messages have this Message-ID (diff)
From: "Emilio López" <emilio@elopez.com.ar>
To: Nick <xerofoify@gmail.com>
Cc: mturquette@linaro.org, maxime.ripard@free-electrons.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHV2]Fixes memory leak in clk-sunxi.c
Date: Sat, 14 Jun 2014 22:31:40 -0300 [thread overview]
Message-ID: <539CF77C.4010500@elopez.com.ar> (raw)
In-Reply-To: <1402794944-3357-1-git-send-email-xerofoify@gmail.com>
Hi,
El 14/06/14 22:15, Nick escribió:
> Signed-off-by: Nick <xerofoify@gmail.com>
> ---
> drivers/clk/sunxi/clk-sunxi.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/clk/sunxi/clk-sunxi.c b/drivers/clk/sunxi/clk-sunxi.c
> index 6f4fc51..c2ce538 100644
> --- a/drivers/clk/sunxi/clk-sunxi.c
> +++ b/drivers/clk/sunxi/clk-sunxi.c
> @@ -41,10 +41,10 @@ static void __init sun4i_osc_clk_setup(struct device_node *node)
> const char *clk_name = node->name;
> u32 rate;
>
> - if (of_property_read_u32(node, "clock-frequency", &rate))
> + if (of_property_read_u32(node, "clock-frequency", &rate)) {
> kree(gate);
> return;
> -
> + }
> /* allocate fixed-rate and gate clock structs */
> fixed = kzalloc(sizeof(struct clk_fixed_rate), GFP_KERNEL);
> if (!fixed)
>
There is no memory leak there, and I think the message was pretty clear
when I mentioned it[1] and then Sergei mentioned it[2] twice[3]. As for
the bug report[4] you linked in a private email, it has been closed as
resolved by the original reporter.
Cheers,
Emilio
[1]
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/263631.html
[2]
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/263677.html
[3]
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/263683.html
[4] https://bugzilla.kernel.org/show_bug.cgi?id=59961
next prev parent reply other threads:[~2014-06-15 1:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-15 1:15 [PATCHV2]Fixes memory leak in clk-sunxi.c Nick
2014-06-15 1:15 ` Nick
2014-06-15 1:31 ` Emilio López [this message]
2014-06-15 1:31 ` Emilio López
2014-06-15 2:00 ` Nick Krause
2014-06-15 2:00 ` Nick Krause
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=539CF77C.4010500@elopez.com.ar \
--to=emilio@elopez.com.ar \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.