From: Daniel Drake <dsd@gentoo.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: Johann Uhrmann <Johann.Uhrmann@gmx.de>,
bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org,
linville@tuxdriver.com
Subject: Re: Belkin F5D7001de locks up my Athlon64 system
Date: Wed, 05 Jul 2006 15:42:44 +0100 [thread overview]
Message-ID: <44ABCFE4.4010808@gentoo.org> (raw)
In-Reply-To: <200607022028.39852.mb@bu3sch.de>
Michael Buesch wrote:
> The following patch is supposed to fix this.
> I did only compile-test it. Please runtime-test it.
>
> Thanks.
>
> --
>
> Softmac Shared Key Auth:
> Fix recursive call into the driver by doing schedule_work.
> recursive calls may result in a driver lock recursion.
Tested on zd1211rw with shared key auth, works fine.
Daniel
prev parent reply other threads:[~2006-07-05 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060701092313.225240@gmx.net>
[not found] ` <200607011828.37874.mb@bu3sch.de>
[not found] ` <20060702113205.16230@gmx.net>
2006-07-02 18:28 ` Belkin F5D7001de locks up my Athlon64 system Michael Buesch
2006-07-05 14:42 ` Daniel Drake [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=44ABCFE4.4010808@gentoo.org \
--to=dsd@gentoo.org \
--cc=Johann.Uhrmann@gmx.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--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).