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