Searched hist:"59 de517d8d482416a079da7ee8344187d513d4a4" (Results 1 – 4 of 4) sorted by relevance
/qemu/tests/unit/ |
H A D | test-io-task.c | 59de517d8d482416a079da7ee8344187d513d4a4 Thu Aug 11 16:38:07 UTC 2016 Daniel P. Berrange <berrange@redhat.com> io: remove Error parameter from QIOTask thread worker
Now that task objects have a directly associated error, there's no need for an an Error **errp parameter to the QIOTask thread worker function. It already has a QIOTask object, so can directly set the error on it.
Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
|
/qemu/io/ |
H A D | task.c | 59de517d8d482416a079da7ee8344187d513d4a4 Thu Aug 11 16:38:07 UTC 2016 Daniel P. Berrange <berrange@redhat.com> io: remove Error parameter from QIOTask thread worker
Now that task objects have a directly associated error, there's no need for an an Error **errp parameter to the QIOTask thread worker function. It already has a QIOTask object, so can directly set the error on it.
Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
|
H A D | channel-socket.c | 59de517d8d482416a079da7ee8344187d513d4a4 Thu Aug 11 16:38:07 UTC 2016 Daniel P. Berrange <berrange@redhat.com> io: remove Error parameter from QIOTask thread worker
Now that task objects have a directly associated error, there's no need for an an Error **errp parameter to the QIOTask thread worker function. It already has a QIOTask object, so can directly set the error on it.
Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
|
/qemu/include/io/ |
H A D | task.h | 59de517d8d482416a079da7ee8344187d513d4a4 Thu Aug 11 16:38:07 UTC 2016 Daniel P. Berrange <berrange@redhat.com> io: remove Error parameter from QIOTask thread worker
Now that task objects have a directly associated error, there's no need for an an Error **errp parameter to the QIOTask thread worker function. It already has a QIOTask object, so can directly set the error on it.
Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
|