.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "I2O_SCSI_REPLY" "" "06 October 2005" "" ""

.SH NAME
i2o_scsi_reply \- scsi message reply processor
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void i2o_scsi_reply  (struct i2o_handler * \fIh\fB, struct i2o_controller * \fIc\fB, struct i2o_message * \fImsg\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIh\fB\fR
our i2o handler
.TP
\fB\fIc\fB\fR
controller issuing the reply
.TP
\fB\fImsg\fB\fR
the message from the controller (mapped)
.SH "DESCRIPTION"
.PP
Process reply messages (interrupts in normal scsi controller think).
We can get a variety of messages to process. The normal path is
scsi command completions. We must also deal with IOP failures,
the reply to a bus reset and the reply to a LUN query.
.SH "LOCKS"
.PP
the queue lock is taken to call the completion handler