scan: Remove unreachable code

We should never reach a point where NEW_SCAN_RESULTS or SCAN_ABORTED are
received before a corresponding TRIGGER_SCAN is received.  Even if this
does happen, there's no harm from processing the commands anyway.
This commit is contained in:
Denis Kenzior 2022-01-18 21:01:41 -06:00
parent c4c86ea1df
commit 280620d7ac
1 changed files with 0 additions and 6 deletions

View File

@ -1844,9 +1844,6 @@ static void scan_notify(struct l_genl_msg *msg, void *user_data)
bool retry = false;
bool get_results = false;
if (sc->state == SCAN_STATE_NOT_RUNNING)
break;
sc->state = SCAN_STATE_NOT_RUNNING;
/* Was this our own scan or an external scan */
@ -1936,9 +1933,6 @@ static void scan_notify(struct l_genl_msg *msg, void *user_data)
break;
case NL80211_CMD_SCAN_ABORTED:
if (sc->state == SCAN_STATE_NOT_RUNNING)
break;
sc->state = SCAN_STATE_NOT_RUNNING;
if (sc->triggered) {