On Thu, 2014-10-16 at 23:25 +0300, Emmanuel Grumbach wrote: > All the callers of ieee80211_mgd_probe_ap_send return right > after they call the flush() callback. This means that calling > flush() is uneeded since its meaning is to wait until the > queues of the device are empty. It is pointless to wait if > there is nothing that must ensure that the frame has left > the Tx queue. > ieee80211_mgd_probe_ap_send is called at the very end of > a worker - so flush() is not needed. There may have been some concern that the timer/work could run again while the packets are still on the (possibly long) queue, but I guess this is reasonable? We might want to avoid that by tracking whether we've sent out a frame and (not) gotten a response? johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
