On 7/18/07, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote:
The neccessary parts get called from libata-eh based upon the flags set by the error code to indicate how to recover.
I see... now let me see if I have this straight: - ata_scsi_pass_thru checks and sees that it's a (soft,hard)reset - sets up eh_info.action with either ATA_EH_HARDRESET or ATA_EH_SOFTRESET - calls ata_port_schedule_eh(ap);
From there, I think the error handler gets queued, but the user
process returns. The other option for the last step would be to call the driver's error_handler directly. This method seems to me like a better solution. - Yasha - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
