All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <jouni@qca.qualcomm.com>
Cc: Sunil Dutt <usdutt@qti.qualcomm.com>,
	linux-wireless@vger.kernel.org, vkanchan@qti.qualcomm.com,
	amarnath@qca.qualcomm.com
Subject: Re: [PATCH 1/2] cfg80211: Add support for aborting an ongoing scan
Date: Fri, 30 Oct 2015 11:58:16 +0100	[thread overview]
Message-ID: <1446202696.3261.24.camel@sipsolutions.net> (raw)
In-Reply-To: <20151030103703.GA6731@jouni.qca.qualcomm.com>

On Fri, 2015-10-30 at 12:37 +0200, Jouni Malinen wrote:
> 
> The currently identified use cases do not seem to care much about the
> actual result of this command since there is going to be a wait for 
> the
> scan completed event anyway and the call is not even used unless 
> there
> is a known ongoing scan. As such, even the difference of a driver
> supporting this command or not is not that significant taken into
> account this is used only as an optimization to speed up the 
> following
> operation when a long scan operation was in progress. Things work 
> fine
> (though without that speed benefit) even if the driver does not
> support this. Anyway, making cfg80211 advertise whether the new 
> command
> is available could obviously be done should someone come up with a 
> use
> case that depends on knowing that the optimization is available.
> 

Fair point. In that case though, making the driver operation void would
make sense.

johannes

      reply	other threads:[~2015-10-30 10:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29  7:46 [PATCH 1/2] cfg80211: Add support for aborting an ongoing scan Sunil Dutt
2015-10-29  7:46 ` [PATCH 2/2] mac80211: " Sunil Dutt
2015-10-30  9:35   ` Johannes Berg
2015-10-30  9:34 ` [PATCH 1/2] cfg80211: " Johannes Berg
2015-10-30 10:37   ` Jouni Malinen
2015-10-30 10:58     ` Johannes Berg [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=1446202696.3261.24.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=amarnath@qca.qualcomm.com \
    --cc=jouni@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=usdutt@qti.qualcomm.com \
    --cc=vkanchan@qti.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.