Alan Stern [EMAIL PROTECTED] wrote: > On 29 Sep 2004, James Bottomley wrote: > > > On Wed, 2004-09-29 at 14:02, Luben Tuikov wrote: > > > > According to Documentation/scsi/scsi_mid_low_api.txt, the only possible > > > > error returns are SCSI_MLQUEUE_DEVICE_BUSY and SCSI_MLQUEUE_HOST_BUSY. > > > > Neither is appropriate; should the second one be returned? > > > > > > I believe internally SCSI Core returns DID_ERROR. > > > > For a device that no-longer exists, DID_NO_CONNECT is probably the most > > appropriately descriptive. > > Regardless of how descriptive the value is, the code in > scsi_dispatch_cmd treats anything other than SCSI_MLQUEUE_DEVICE_BUSY > as SCSI_MLQUEUE_HOST_BUSY. Will this matter? >
You would not want to return non zero status from your queucommand, but set the result of the command to DID_NO_CONNECT and call done. -andmike -- Michael Anderson [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
