bearer-qmi: fix logic if error setting up WDS event report indications

If we get an error when setting up the WDS event report indications,
make sure we run connect_context_step() after having set the next step
as CONNECT_STEP_LAST.

(cherry picked from commit 850107acbfe3878326b695d4ea31f02d2321aa22)

1 files changed, 8 insertions, 8 deletions

diff --git a/src/mm-bearer-qmi.c b/src/mm-bearer-qmi.c
index d3e692ea..81510304 100644
--- a/src/mm-bearer-qmi.c
+++ b/src/mm-bearer-qmi.c
@@ -896,12 +896,12 @@ connect_enable_indications_ipv4_ready (QmiClientWds *client,
 
     ctx->event_report_ipv4_indication_id =
         connect_enable_indications_ready (client, res, ctx->self, &ctx->error_ipv4);
-    if (!ctx->event_report_ipv4_indication_id) {
+
+    if (!ctx->event_report_ipv4_indication_id)
         ctx->step = CONNECT_STEP_LAST;
-        return;
-    }
+    else
+        ctx->step++;
 
-    ctx->step++;
     connect_context_step (ctx);
 }
 
@@ -914,12 +914,12 @@ connect_enable_indications_ipv6_ready (QmiClientWds *client,
 
     ctx->event_report_ipv6_indication_id =
         connect_enable_indications_ready (client, res, ctx->self, &ctx->error_ipv6);
-    if (!ctx->event_report_ipv6_indication_id) {
+
+    if (!ctx->event_report_ipv6_indication_id)
         ctx->step = CONNECT_STEP_LAST;
-        return;
-    }
+    else
+        ctx->step++;
 
-    ctx->step++;
     connect_context_step (ctx);
 }