linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211:  Support on-channel scan option.
Date: Sun, 01 Apr 2012 13:45:27 -0700	[thread overview]
Message-ID: <4F78BE67.8090609@candelatech.com> (raw)
In-Reply-To: <1333305916.3703.2.camel@jlt3.sipsolutions.net>

On 04/01/2012 11:45 AM, Johannes Berg wrote:
> On Sat, 2012-03-31 at 15:30 -0700, greearb@candelatech.com wrote:
>
>
>>   static int __ieee80211_start_scan(struct ieee80211_sub_if_data *sdata,
>>   				  struct cfg80211_scan_request *req)
>> @@ -438,6 +461,33 @@ static int __ieee80211_start_scan(struct ieee80211_sub_if_data *sdata,
>>   	local->scan_req = req;
>>   	local->scan_sdata = sdata;
>>
>> +	/* If we are scanning only on the current channel, then
>> +	 * we do not need to stop normal activities
>> +	 */
>> +	if ((req->n_channels == 1)&&
>> +	    (req->channels[0]->center_freq ==
>> +	     local->hw.conf.channel->center_freq)) {
> ...
>> +		return 0;
>> +	}
>> +
>>   	if (local->ops->hw_scan)
>>   		__set_bit(SCAN_HW_SCANNING,&local->scanning);
>
> Clearly, you're joking.

That is worthless feedback and gives me no idea what you
think should be fixed about it.

If you hate the entire idea of optimizing scanning on channel,
just say so plainly.

Ben

>
> johannes


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2012-04-01 20:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-31 22:30 [RFC] mac80211: Support on-channel scan option greearb
2012-04-01 18:45 ` Johannes Berg
2012-04-01 20:45   ` Ben Greear [this message]
2012-04-01 20:49     ` Johannes Berg
2012-04-01 20:53       ` Ben Greear
2012-04-01 21:11         ` Johannes Berg
2012-04-01 21:25           ` 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=4F78BE67.8090609@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --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).