Lines Matching refs:complete
17 calls and complete() instead.
40 - the signaling side through a call to complete() or complete_all().
65 complete(&early_console_added);
68 'complete' is not helpful unless the purpose is super obvious...
76 to prevent races with asynchronous complete() calls from occurring.
80 does not happen until all related activities (complete() or reinit_completion())
127 _killable() and _interruptible()) variants, the wait might complete
130 stack and cause subtle data corruption if a complete() is done in some
136 or has a lock or other synchronization mechanism to make sure complete()
160 wait_for_completion(&setup_done); complete(setup_done);
163 the call to complete() - if the call to complete() happened before the call
166 completion is signaled by complete().
247 achieved calls complete() to signal exactly one of the waiters that it can
250 void complete(struct completion *done)
261 If complete() is called multiple times then this will allow for that number
262 of waiters to continue - each call to complete() will simply increment the
264 complete() and complete_all() can be called in IRQ/atomic context safely.
266 There can only be one thread calling complete() or complete_all() on a
268 queue spinlock. Any such concurrent calls to complete() or complete_all()