Documentation/scheduler/completion.rst

129 from the wait_on_completion*() caller function will deallocate the function
164 to wait_for_completion() then the waiting side simply will continue
165 immediately as all dependencies are satisfied; if not, it will block until
170 Calling it from IRQs-off atomic contexts will result in hard-to-detect
207 If a signal was received while waiting it will return -ERESTARTSYS; 0 otherwise::
211 The task is marked as TASK_UNINTERRUPTIBLE and will wait at most 'timeout'
224 TASK_INTERRUPTIBLE. If a signal was received it will return -ERESTARTSYS;
229 designated tasks state and will return -ERESTARTSYS if it is interrupted,
256 The signaling will work as expected even if completions are signaled before
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
271 Signaling completion from IRQ context is fine as it will appropriately
272 lock with spin_lock_irqsave()/spin_unlock_irqrestore() and it will never
279 The try_wait_for_completion() function will not put the thread on the wait