summaryrefslogtreecommitdiff
path: root/drivers/s390/scsi/zfcp_scsi.c
diff options
context:
space:
mode:
authorChristof Schmitt <christof.schmitt@de.ibm.com>2009-11-24 15:54:15 (GMT)
committerJames Bottomley <James.Bottomley@suse.de>2009-12-04 18:02:16 (GMT)
commit4c571c659e9d41332b6981ca5379047681ce9d2f (patch)
tree57221fdc1d2e0450dbed56e0255ff1ddf14a861a /drivers/s390/scsi/zfcp_scsi.c
parentee744622c65cd66824e8dd1b9509e515c800de14 (diff)
downloadlinux-fsl-qoriq-4c571c659e9d41332b6981ca5379047681ce9d2f.tar.xz
[SCSI] zfcp: Update FSF error reporting
The SCSI midlayer retries commands based on the remote port state and the command status reported by the driver. Returning DID_TRANSPORT_DISRUPTED is a better approach, use this for reporting FSF errors back to the SCSI midlayer. See http://marc.info/?l=linux-scsi&m=125668044215051&w=2 as reference. There is also no need in special treatment of ABORTED commands, so remove the ZFCP_STATUS_FSFREQ_ABORTED, the commands are then returned with DID_TRANSPORT_DISRUPTED. Also remove the ZFCP_STATUS_FSFREQ_RETRY: It is useless, no retry is happening in the FSF layer and nobody checks the state of this flag. Reviewed-by: Swen Schillig <swen@vnet.ibm.com> Signed-off-by: Christof Schmitt <christof.schmitt@de.ibm.com> Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'drivers/s390/scsi/zfcp_scsi.c')
0 files changed, 0 insertions, 0 deletions