From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Chen Tao <chentao107@huawei.com>,
linux-omap@vger.kernel.org, linux@armlinux.org.uk,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP2+: Fix possible memory leak in omap_hwmod_allocate_module
Date: Mon, 13 Jul 2020 09:47:53 -0700 [thread overview]
Message-ID: <20200713164753.GM5849@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.21.999.2006191518380.26224@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [200619 15:20]:
> On Fri, 19 Jun 2020, Chen Tao wrote:
>
> > Fix memory leak in omap_hwmod_allocate_module not freeing in
> > handling error path.
> >
> > Fixes: 8c87970543b17("ARM: OMAP2+: Add functions to allocate module data from device tree")
> > Signed-off-by: Chen Tao <chentao107@huawei.com>
>
> Reviewed-by: Paul Walmsley <paul@pwsan.com>
Thanks applying into fixes.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Chen Tao <chentao107@huawei.com>,
linux-omap@vger.kernel.org, linux@armlinux.org.uk,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP2+: Fix possible memory leak in omap_hwmod_allocate_module
Date: Mon, 13 Jul 2020 09:47:53 -0700 [thread overview]
Message-ID: <20200713164753.GM5849@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.21.999.2006191518380.26224@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [200619 15:20]:
> On Fri, 19 Jun 2020, Chen Tao wrote:
>
> > Fix memory leak in omap_hwmod_allocate_module not freeing in
> > handling error path.
> >
> > Fixes: 8c87970543b17("ARM: OMAP2+: Add functions to allocate module data from device tree")
> > Signed-off-by: Chen Tao <chentao107@huawei.com>
>
> Reviewed-by: Paul Walmsley <paul@pwsan.com>
Thanks applying into fixes.
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-07-13 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 10:42 [PATCH] ARM: OMAP2+: Fix possible memory leak in omap_hwmod_allocate_module Chen Tao
2020-06-19 10:42 ` Chen Tao
2020-06-19 15:18 ` Paul Walmsley
2020-06-19 15:18 ` Paul Walmsley
2020-07-13 16:47 ` Tony Lindgren [this message]
2020-07-13 16:47 ` 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=20200713164753.GM5849@atomide.com \
--to=tony@atomide.com \
--cc=chentao107@huawei.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=paul@pwsan.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 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.