From: Tony Lindgren <tony@atomide.com>
To: Youling Tang <tangyouling@loongson.cn>
Cc: Russell King <linux@armlinux.org.uk>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] arm: Fix memleak in omap2xxx_clkt_vps_init
Date: Thu, 19 Nov 2020 11:54:09 +0200 [thread overview]
Message-ID: <20201119095409.GN26857@atomide.com> (raw)
In-Reply-To: <1605326818-13823-1-git-send-email-tangyouling@loongson.cn>
* Youling Tang <tangyouling@loongson.cn> [201114 04:07]:
> If the clk_register fails, we should free hw before function returns to
> prevent memleak.
Thanks applying both into omap-for-v5.11/soc.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Youling Tang <tangyouling@loongson.cn>
Cc: linux-omap@vger.kernel.org, Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] arm: Fix memleak in omap2xxx_clkt_vps_init
Date: Thu, 19 Nov 2020 11:54:09 +0200 [thread overview]
Message-ID: <20201119095409.GN26857@atomide.com> (raw)
In-Reply-To: <1605326818-13823-1-git-send-email-tangyouling@loongson.cn>
* Youling Tang <tangyouling@loongson.cn> [201114 04:07]:
> If the clk_register fails, we should free hw before function returns to
> prevent memleak.
Thanks applying both into omap-for-v5.11/soc.
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-19 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 4:06 [PATCH 1/2] arm: Fix memleak in omap2xxx_clkt_vps_init Youling Tang
2020-11-14 4:06 ` Youling Tang
2020-11-19 9:54 ` Tony Lindgren [this message]
2020-11-19 9:54 ` Tony Lindgren
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=20201119095409.GN26857@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=tangyouling@loongson.cn \
/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.