From: David Miller <davem@davemloft.net>
To: jcliburn@gmail.com
Cc: jslaby@suse.cz, linux-kernel@vger.kernel.org,
jirislaby@gmail.com, chris.snook@gmail.com, jie.yang@atheros.com,
atl1-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH 1/1] NET: atlx, fix memory leak
Date: Thu, 07 Jan 2010 01:05:06 -0800 (PST) [thread overview]
Message-ID: <20100107.010506.165517428.davem@davemloft.net> (raw)
In-Reply-To: <20100106182830.4bd861fe@gmail.com>
From: J K Cliburn <jcliburn@gmail.com>
Date: Wed, 6 Jan 2010 18:28:30 -0600
> On Wed, 6 Jan 2010 17:54:16 +0100
> Jiri Slaby <jslaby@suse.cz> wrote:
>
>> Stanse found a memory leak in atl2_get_eeprom. eeprom_buff is not
>> freed/assigned on all paths. Fix that.
>
> Acked by: Jay Cliburn <jcliburn@gmail.com>
Applied, thanks.
prev parent reply other threads:[~2010-01-07 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 16:54 [PATCH 1/1] NET: atlx, fix memory leak Jiri Slaby
2010-01-07 0:28 ` J K Cliburn
2010-01-07 9:05 ` David Miller [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=20100107.010506.165517428.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=atl1-devel@lists.sourceforge.net \
--cc=chris.snook@gmail.com \
--cc=jcliburn@gmail.com \
--cc=jie.yang@atheros.com \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).