From 9402841d991ef0329f8efdfc6b91f9214950555e Mon Sep 17 00:00:00 2001
From: Jarek Kobus <jaroslaw.kobus@qt.io>
Date: Mon, 2 May 2022 20:06:46 +0200
Subject: [PATCH] QtcProcess: Fix runBlocking() on remote

There is no need for special handling when running on remote.

Change-Id: If30245d2ece475cb72df2be4390210d6b8c0c1aa
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
---
 src/libs/utils/qtcprocess.cpp | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/src/libs/utils/qtcprocess.cpp b/src/libs/utils/qtcprocess.cpp
index 81ccca37603..2d7a4bfb60a 100644
--- a/src/libs/utils/qtcprocess.cpp
+++ b/src/libs/utils/qtcprocess.cpp
@@ -1783,14 +1783,6 @@ static bool isGuiThread()
 
 void QtcProcess::runBlocking(EventLoopMode eventLoopMode)
 {
-    // FIXME: Implement properly
-
-    if (d->m_setup.m_commandLine.executable().needsDevice()) {
-        QtcProcess::start();
-        waitForFinished();
-        return;
-    };
-
     if (processLog().isDebugEnabled()) {
         // Attach a dynamic property with info about blocking type
         setProperty(QTC_PROCESS_BLOCKING_TYPE, int(eventLoopMode));