From: Bob Copeland <me@bobcopeland.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org,
"Eugene A. Shatokhin" <dame_eugene@mail.ru>,
Nick Kossifidis <mickflemm@gmail.com>,
ath5k-devel@venema.h4ckr.net
Subject: Re: [PATCH] ath5k: improve pcal error handling for ENOMEM case
Date: Sat, 9 Apr 2011 09:22:46 -0400 [thread overview]
Message-ID: <20110409132246.GD18154@hash.lan> (raw)
In-Reply-To: <1302291192-19249-1-git-send-email-linville@tuxdriver.com>
On Fri, Apr 08, 2011 at 03:33:12PM -0400, John W. Linville wrote:
> The ath5k driver does kmalloc allocations for pcal info in a loop.
> But, if one fails it was simply returning -ENOMEM without freeing
> already allocated memory. This patch corrects that oversight.
>
> Reported-by: Eugene A. Shatokhin <dame_eugene@mail.ru>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Reviewed-by: Bob Copeland <me@bobcopeland.com>
Thanks!
--
Bob Copeland %% www.bobcopeland.com
prev parent reply other threads:[~2011-04-09 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 19:33 [PATCH] ath5k: improve pcal error handling for ENOMEM case John W. Linville
2011-04-09 13:22 ` Bob Copeland [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=20110409132246.GD18154@hash.lan \
--to=me@bobcopeland.com \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=dame_eugene@mail.ru \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mickflemm@gmail.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.