From: Alan Cox <alan@linux.intel.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] Staging: intel_sst: fix memory leak
Date: Tue, 16 Nov 2010 13:38:37 +0000 [thread overview]
Message-ID: <20101116133837.19074497@linux.intel.com> (raw)
In-Reply-To: <20101113085826.GM3533@bicker>
On Sat, 13 Nov 2010 11:58:26 +0300
Dan Carpenter <error27@gmail.com> wrote:
> The original code set "str_info->decode_ibuf" to NULL so the kfree()
> is no-op.
>
> Signed-off-by: Dan Carpenter <error27@gmail.com>
> ---
> This is a static checker thing. I don't have the hardware to test
> this myself so please check it carefully.
Acked-by: Alan Cox <alan@linux.intel.com>
prev parent reply other threads:[~2010-11-16 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-13 8:58 [patch] Staging: intel_sst: fix memory leak Dan Carpenter
2010-11-15 5:47 ` Harsha, Priya
2010-11-16 13:38 ` Alan Cox [this message]
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=20101116133837.19074497@linux.intel.com \
--to=alan@linux.intel.com \
--cc=kernel-janitors@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox