Lines Matching full:upon
47 * @done: The callback routine the LLDD is to invoke upon completion of
49 * request structure. Status argument must be 0 upon success, a
91 * Upon completion of the LS response transmit, the LLDD will pass the
93 * allowing the transport release dma resources. Upon completion of
104 * to be called upon completion of the transmit. The transport layer
112 * @done: The callback routine the LLDD is to invoke upon completion of
188 * @done: The callback routine the LLDD is to invoke upon completion of
202 * @status: Completion status of the FCP operation. must be 0 upon success,
203 * negative errno value upon failure (ex: -EIO). Note: this is
349 * asynchronous. This routine is called upon the completion of the
355 * asynchronous. This routine is called upon the completion of the
359 * @create_queue: Upon creating a host<->controller association, queues are
363 * or map it onto a shared hw queue. Upon return from the call, the
420 * non-zero errno status), and upon completion of the transmit, call
423 * itself). Upon the completion of the done routine, the LLDD shall
620 * FCP I/O, and any FC exchange context. Upon completion of the FCP target
623 * Upon completion of the done() routine for either RSP or ABORT ops, no
634 * upon compeletion of the operation. The nvmet-fc layer will also set a
665 * @done: The callback routine the LLDD is to invoke upon completion of
762 * asynchronous. This routine is called upon the completion of the
772 * non-zero errno status), and upon completion of the transmit, call
775 * itself). Upon the completion of the done() routine, the LLDD shall
811 * may retramsit the FCP_RSP iu if necessary per FC-NVME. Upon
813 * or upon success/failure of FCP_CONF if it is supported, the
820 * FCP_RSP iu if FCP_CONF is not received per FC-NVME. Upon
822 * or upon success/failure of FCP_CONF if it is supported, the
825 * Upon completing the indicated operation, the LLDD is to set the
859 * This may be due to the command completing or upon completion of