P2P: Do not consider the p2p_scan results after p2p_stop_find
authorSunil Dutt <usdutt@qti.qualcomm.com>
Thu, 30 Oct 2014 15:21:52 +0000 (20:51 +0530)
committerJouni Malinen <j@w1.fi>
Thu, 30 Oct 2014 22:50:01 +0000 (00:50 +0200)
commit477b082cc4e9cb2025dba83bab6f9eed47eefc05
tree3d45465a6414b8a20931057e9fdabcfc9ad8fd25
parentb5ea99377f852f913b52ed146ab30ff1a1a0e141
P2P: Do not consider the p2p_scan results after p2p_stop_find

If p2p_stop_find is issued after the p2p_scan request is triggered to
the host driver, the obtained scan results are also considered to update
the P2P peer entries. This is not always desired behavior, i.e., it can
be clearer if no P2P-DEVICE-FOUND events are generated based of that
final pending scan.

Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
wpa_supplicant/ctrl_iface.c
wpa_supplicant/p2p_supplicant.c