From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: Ameya Palande <ameya.palande@nokia.com>
Cc: "Menon, Nishanth" <nm@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Chitriki Rudramuni, Deepak" <deepak.chitriki@ti.com>
Subject: Re: [PATCHv2] DSPBRIDGE: Fix memory leak in PROC_AutoStart()
Date: Fri, 5 Feb 2010 19:57:58 -0600 [thread overview]
Message-ID: <4B6CCCA6.6080006@ti.com> (raw)
In-Reply-To: <ea29f699c0916873d206c498bbf41a610a53492d.1265045613.git.ameya.palande@nokia.com>
On 2/1/2010 11:36 AM, Ameya Palande wrote:
> Signed-off-by: Ameya Palande<ameya.palande@nokia.com>
Acked-by: Omar Ramirez Luna <omar.ramirez@ti.com>
> ---
> drivers/dsp/bridge/rmgr/proc.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/dsp/bridge/rmgr/proc.c b/drivers/dsp/bridge/rmgr/proc.c
> index 491661f..ff3329f 100644
> --- a/drivers/dsp/bridge/rmgr/proc.c
> +++ b/drivers/dsp/bridge/rmgr/proc.c
> @@ -411,6 +411,8 @@ DSP_STATUS PROC_AutoStart(struct CFG_DEVNODE *hDevNode,
> "No Exec file found \n");
> }
> func_cont:
> + MEM_Free(hProcObject->g_pszLastCoff);
> + hProcObject->g_pszLastCoff = NULL;
> MEM_FreeObject(hProcObject);
> func_end:
> GT_1trace(PROC_DebugMask, GT_ENTER,
Pushed to dspbridge.
- omar
next prev parent reply other threads:[~2010-02-06 1:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 13:03 [PATCH] DSPBRIDGE: Fix memory leak in PROC_AutoStart() Ameya Palande
2010-01-25 19:21 ` Omar Ramirez Luna
2010-02-01 17:31 ` Ameya Palande
2010-02-01 17:36 ` [PATCHv2] " Ameya Palande
2010-02-06 1:57 ` Omar Ramirez Luna [this message]
2010-02-06 0:58 ` [PATCH] " Omar Ramirez Luna
-- strict thread matches above, loose matches on Subject: below --
2009-09-02 18:59 Ameya Palande
2009-09-02 19:07 ` [PATCHv2] " Ameya Palande
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=4B6CCCA6.6080006@ti.com \
--to=omar.ramirez@ti.com \
--cc=ameya.palande@nokia.com \
--cc=deepak.chitriki@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.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.