From: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
To: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
Cc: Ulrich Kunitz <kune-hUSrv6EASfkEnNRfnnE9gw@public.gmane.org>,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Stefano Brivio <st3-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>,
John Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Subject: Re: [PATCH] softmac: Fixed handling of deassociation from AP
Date: Thu, 7 Dec 2006 10:50:51 +0100 [thread overview]
Message-ID: <200612071050.51900.mb@bu3sch.de> (raw)
In-Reply-To: <45776228.2050005-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
On Thursday 07 December 2006 01:36, Larry Finger wrote:
> it seems to
> me that the mutex protects only the association data; whereas the spinlock protects more data, but
> does include the association data.
Nope.
The same way you could argue that the BKL should be taken here,
as it's "the global kernel lock which protects everything".
But it's simply not true and won't protect anything. ;)
--
Greetings Michael.
next prev parent reply other threads:[~2006-12-07 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 14:45 [PATCH] softmac: Fixed handling of deassociation from AP Larry Finger
2006-12-06 17:52 ` Michael Buesch
2006-12-06 20:17 ` Ulrich Kunitz
2006-12-06 20:52 ` Michael Buesch
2006-12-06 21:51 ` Ulrich Kunitz
2006-12-06 22:51 ` Michael Buesch
2006-12-07 0:36 ` Larry Finger
[not found] ` <45776228.2050005-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-12-07 9:50 ` Michael Buesch [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-03 15:32 Ulrich Kunitz
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=200612071050.51900.mb@bu3sch.de \
--to=mb-fseuscv1ubazqb+pc5nmwq@public.gmane.org \
--cc=Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org \
--cc=kune-hUSrv6EASfkEnNRfnnE9gw@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=st3-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.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).