Lines Matching refs:complete
175 complete(&msginfo->waitevent);
816 * functional and vmbus_unload_response() will complete
822 * complete. This flushing has been empirically observed to take up
859 complete(&vmbus_connection.unload_event);
869 pr_notice("Waiting for VMBus UNLOAD to complete\n");
873 pr_err("Continuing even though VMBus UNLOAD did not complete\n");
905 * of the complete() below. Make sure that unload_event has been
906 * initialized by the time this complete() is executed.
908 complete(&vmbus_connection.unload_event);
945 complete(&vmbus_connection.ready_for_resume_event);
1130 complete(&vmbus_connection.ready_for_suspend_event);
1215 * Now wait for offer handling to complete.
1264 complete(&channel->rescind_event);
1337 complete(&msginfo->waitevent);
1386 complete(&msginfo->waitevent);
1426 complete(&msginfo->waitevent);
1473 complete(&msginfo->waitevent);
1512 complete(&msginfo->waitevent);