From: David Miller <davem@davemloft.net>
To: rmody@brocade.com
Cc: netdev@vger.kernel.org, ddutt@brocade.com
Subject: Re: [PATCH 2/2] bna: fix memory leak during RX path cleanup
Date: Thu, 14 Apr 2011 13:40:03 -0700 (PDT) [thread overview]
Message-ID: <20110414.134003.71113677.davem@davemloft.net> (raw)
In-Reply-To: <1302804319-15677-2-git-send-email-rmody@brocade.com>
From: Rasesh Mody <rmody@brocade.com>
Date: Thu, 14 Apr 2011 11:05:19 -0700
> The memory leak was caused by unintentional assignment of the Rx path
> destroy callback function pointer to NULL just after correct
> initialization.
>
> Signed-off-by: Debashis Dutt <ddutt@brocade.com>
> Signed-off-by: Rasesh Mody <rmody@brocade.com>
Applied.
next prev parent reply other threads:[~2011-04-14 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 18:05 [PATCH 1/2] bna: fix for clean fw re-initialization Rasesh Mody
2011-04-14 18:05 ` [PATCH 2/2] bna: fix memory leak during RX path cleanup Rasesh Mody
2011-04-14 20:40 ` David Miller [this message]
2011-04-14 20:39 ` [PATCH 1/2] bna: fix for clean fw re-initialization David Miller
2011-04-18 19:26 ` Rasesh Mody
2011-04-18 19:28 ` David Miller
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=20110414.134003.71113677.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ddutt@brocade.com \
--cc=netdev@vger.kernel.org \
--cc=rmody@brocade.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).