From: Oliver Neukum <oliver@neukum.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, Michael Wu <flamingice@sourmilk.net>,
Andrea Merello <andreamrl@tiscali.it>
Subject: Re: [patch] resource leak in error case in rtl8187
Date: Thu, 15 May 2008 21:46:54 +0200 [thread overview]
Message-ID: <200805152146.55673.oliver@neukum.org> (raw)
In-Reply-To: <20080515185724.GA17690@tuxdriver.com>
Am Donnerstag 15 Mai 2008 20:57:24 schrieb John W. Linville:
> Don't we need the same type of fix applied to rtl8187_iowrite_async
> as well? Would you like to resubmit (or submit a second patch)
> with that fix included?
Indeed. A new redone patch is on the way. Please disregard the earlier patch.
Regards
Oliver
prev parent reply other threads:[~2008-05-15 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 14:17 [patch] resource leak in error case in rtl8187 Oliver Neukum
2008-05-15 18:57 ` John W. Linville
2008-05-15 19:46 ` Oliver Neukum [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=200805152146.55673.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=andreamrl@tiscali.it \
--cc=flamingice@sourmilk.net \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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).