From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: Scanning improvements for multiple VIFS.
Date: Sat, 13 Nov 2010 06:19:56 +0100 [thread overview]
Message-ID: <4b2689e6064549781b072ac8956bcc1a@localhost> (raw)
In-Reply-To: <4CDDE324.3070801@candelatech.com>
>> In nl80211_trigger_scan, if rdev->scan_req is != NULL,
>> instead of returning EBUSY, what if we set a flag in
>> the VIF that said "I want scan results too."
>>
>> Then, when whatever is scanning is finished, it would send
>> scan results to all interested vifs.
But the scans results could technically be different
if they've been done on a different interface. Besides,
you can handle it in userspace. You've been trying for
weeks to avoid changing your userspace by changing the
kernel, which is still the wrong approach.
johannes
next prev parent reply other threads:[~2010-11-13 5:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 23:23 Scanning improvements for multiple VIFS Ben Greear
2010-11-13 1:00 ` Ben Greear
2010-11-13 5:19 ` Johannes Berg [this message]
2010-11-13 18:19 ` Ben Greear
2010-11-15 19:10 ` Ben Greear
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=4b2689e6064549781b072ac8956bcc1a@localhost \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@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).