From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Williams <dcbw@redhat.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [wt PATCH 5/5] libertas: scan before assocation if no BSSID was given
Date: Fri, 30 Jul 2010 08:37:18 +0200 [thread overview]
Message-ID: <1280471838.3710.6.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1280470711.14523.16.camel@dcbw.foobar.com>
On Thu, 2010-07-29 at 23:18 -0700, Dan Williams wrote:
> Fix this leftover TODO from the cfg80211 conversion by doing a scan
> if cfg80211 didn't pass in the BSSID for us. Since the scan code
> uses so much of the cfg80211_scan_request structure to build up the
> firmware command, we just fake one when the scan request is triggered
> internally. But we need to make sure that internal 'fake' cfg82011
> scan request does get back to cfg82011 via cfg80211_scan_done().
I think you mean "does _not_ get back".
johannes
next prev parent reply other threads:[~2010-07-30 6:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 6:07 [wt PATCH 0/5] libertas: make association work again Dan Williams
2010-07-30 6:11 ` [wt PATCH 1/5] libertas: get the right # of scanned BSSes Dan Williams
2010-07-30 6:12 ` [wt PATCH 2/5] libertas: better scan response debugging Dan Williams
2010-07-30 6:14 ` [wt PATCH 3/5] libertas: better association request debugging Dan Williams
2010-07-30 6:16 ` [wt PATCH 4/5] libertas: fix association with some APs by using extended rates Dan Williams
2010-07-30 6:18 ` [wt PATCH 5/5] libertas: scan before assocation if no BSSID was given Dan Williams
2010-07-30 6:37 ` Johannes Berg [this message]
2010-08-04 5:43 ` [wt PATCH 5/5 v2] " Dan Williams
2010-07-30 6:35 ` [wt PATCH 0/5] libertas: make association work again Johannes Berg
2010-07-31 13:54 ` Holger Schurig
2010-08-04 5:41 ` Dan Williams
2010-08-04 7:46 ` Johannes Berg
2010-08-04 19:15 ` Dan Williams
2010-08-04 19:34 ` John W. Linville
2010-08-05 17:27 ` Dan Williams
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=1280471838.3710.6.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--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).