Lines Matching full:upon
48 * @done: The callback routine the LLDD is to invoke upon completion of
50 * request structure. Status argument must be 0 upon success, a
92 * Upon completion of the LS response transmit, the LLDD will pass the
94 * allowing the transport release dma resources. Upon completion of
105 * to be called upon completion of the transmit. The transport layer
113 * @done: The callback routine the LLDD is to invoke upon completion of
189 * @done: The callback routine the LLDD is to invoke upon completion of
203 * @status: Completion status of the FCP operation. must be 0 upon success,
204 * negative errno value upon failure (ex: -EIO). Note: this is
350 * asynchronous. This routine is called upon the completion of the
356 * asynchronous. This routine is called upon the completion of the
360 * @create_queue: Upon creating a host<->controller association, queues are
364 * or map it onto a shared hw queue. Upon return from the call, the
421 * non-zero errno status), and upon completion of the transmit, call
424 * itself). Upon the completion of the done routine, the LLDD shall
632 * FCP I/O, and any FC exchange context. Upon completion of the FCP target
635 * Upon completion of the done() routine for either RSP or ABORT ops, no
646 * upon compeletion of the operation. The nvmet-fc layer will also set a
677 * @done: The callback routine the LLDD is to invoke upon completion of
774 * asynchronous. This routine is called upon the completion of the
784 * non-zero errno status), and upon completion of the transmit, call
787 * itself). Upon the completion of the done() routine, the LLDD shall
827 * may retramsit the FCP_RSP iu if necessary per FC-NVME. Upon
829 * or upon success/failure of FCP_CONF if it is supported, the
836 * FCP_RSP iu if FCP_CONF is not received per FC-NVME. Upon
838 * or upon success/failure of FCP_CONF if it is supported, the
841 * Upon completing the indicated operation, the LLDD is to set the
875 * This may be due to the command completing or upon completion of