From: "Franky Lin" <frankyl@broadcom.com>
To: "Dan Carpenter" <dan.carpenter@oracle.com>,
"John W. Linville" <linville@tuxdriver.com>
Cc: "Arend Van Spriel" <arend@broadcom.com>,
"Pieter-Paul Giesberts" <pieterpg@broadcom.com>,
"Alwin Beukers" <alwin@broadcom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>
Subject: Re: [patch] brcm80211: fmac: small memory leak on error
Date: Wed, 30 Nov 2011 10:42:45 -0800 [thread overview]
Message-ID: <4ED67925.6040603@broadcom.com> (raw)
In-Reply-To: <20111130084937.GI6268@elgon.mountain>
On 11/30/2011 12:49 AM, Dan Carpenter wrote:
> We should free "bus_if" here, it's a small leak but it makes the static
> checkers happy.
>
> Signed-off-by: Dan Carpenter<dan.carpenter@oracle.com>
Thanks, Dan.
Acked-by: Franky Lin <frankyl@broadcom.com>
Franky
prev parent reply other threads:[~2011-11-30 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 8:49 [patch] brcm80211: fmac: small memory leak on error Dan Carpenter
2011-11-30 18:42 ` Franky Lin [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=4ED67925.6040603@broadcom.com \
--to=frankyl@broadcom.com \
--cc=alwin@broadcom.com \
--cc=arend@broadcom.com \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=pieterpg@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).