On Fri, Sep 21, 2018 at 10:28:55AM +0200, Wolfgang Bumiller wrote:
> monitor_resume() and monitor_suspend() both want to
> "kick" the I/O thread if it is there, but in
> monitor_suspend() lacked the use_io_thread flag condition.
> This is required when we later only spawn the thread on
> first use.
On 9/21/18 3:28 AM, Wolfgang Bumiller wrote:
monitor_resume() and monitor_suspend() both want to
"kick" the I/O thread if it is there, but in
monitor_suspend() lacked the use_io_thread flag condition.
This is required when we later only spawn the thread on
first use.
When sending a multi-patch
monitor_resume() and monitor_suspend() both want to
"kick" the I/O thread if it is there, but in
monitor_suspend() lacked the use_io_thread flag condition.
This is required when we later only spawn the thread on
first use.
Signed-off-by: Wolfgang Bumiller
---
monitor.c | 2 +-
1 file changed, 1
