diff options
author | Christof Schmitt <christof.schmitt@de.ibm.com> | 2009-07-13 15:06:09 +0200 |
---|---|---|
committer | James Bottomley <James.Bottomley@HansenPartnership.com> | 2009-07-30 08:49:57 -0500 |
commit | 85600f7f8370fe5b4be0debd8b401de7986b52ae (patch) | |
tree | 04b35f05814a74b3b1e5e71abd722ee164b3ca9c /crypto/cast6.c | |
parent | ddb3e0c111fed0a8bf74884dc918274acec2b618 (diff) |
[SCSI] zfcp: Fix erp escalation procedure
If an action fails, retry it until the erp count exceeds the
threshold. If there is something fundamentally wrong, the FSF layer
will trigger a more appropriate action depending on the FSF status
codes.
The followup for successful actions is a different followup than
retrying failed actions, so split the code two functions to make this
clear.
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@HansenPartnership.com>
Diffstat (limited to 'crypto/cast6.c')
0 files changed, 0 insertions, 0 deletions