From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Matthieu CASTET <castet.matthieu@free.fr>,
linux-wireless@vger.kernel.org,
Larry Finger <Larry.Finger@lwfinger.net>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] b43/legacy: fix beacon change processing
Date: Mon, 18 May 2009 20:19:55 +0200 [thread overview]
Message-ID: <200905182019.56184.mb@bu3sch.de> (raw)
In-Reply-To: <1242636798.8425.2.camel@johannes.local>
On Monday 18 May 2009 10:53:18 Johannes Berg wrote:
> Process beacon change even if the BSSID doesn't
> change at the same time. Also fix what I think
ACK.
> is a small locking error in b43legacy, there's
> a spin_unlock_irqrestore that looks out of place.
Yeah, I think a patch was already submitted by larry.
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
--
Greetings, Michael.
prev parent reply other threads:[~2009-05-18 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 20:31 B43 no beacon ? Matthieu CASTET
2009-05-12 22:39 ` Matthieu CASTET
2009-05-18 8:53 ` [PATCH] b43/legacy: fix beacon change processing Johannes Berg
2009-05-18 18:19 ` Michael Buesch [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=200905182019.56184.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=castet.matthieu@free.fr \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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).