aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAl Viro <viro@ZenIV.linux.org.uk>2012-12-07 09:10:14 -0500
committerRobert Love <robert.w.love@intel.com>2012-12-14 13:38:56 -0500
commit4f670ff8eb4cb3e9e6ae0c0c6976faa0a4503751 (patch)
tree2cc6bff4f495a283921f01c50e5954d76db92086
parentb8b3e697d15165090583bed850879b1f3b250db0 (diff)
debris left by "[SCSI] libfcoe: Remove mutex_trylock/restart_syscall checks"
AFAICS, the situation for fcoe_transport_disable() seems to be the same as for fcoe_transport_enable(). IOW, shouldn't it have restart_syscall() removed as well? I don't see any in-tree ->disable() instances that could return -ERESTARTSYS, anyway... Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Robert Love <robert.w.love@intel.com>
-rw-r--r--drivers/scsi/fcoe/fcoe_transport.c6
1 files changed, 1 insertions, 5 deletions
diff --git a/drivers/scsi/fcoe/fcoe_transport.c b/drivers/scsi/fcoe/fcoe_transport.c
index dd1aeb45f4cd..f3a5a53e8631 100644
--- a/drivers/scsi/fcoe/fcoe_transport.c
+++ b/drivers/scsi/fcoe/fcoe_transport.c
@@ -962,11 +962,7 @@ out_putdev:
962 dev_put(netdev); 962 dev_put(netdev);
963out_nodev: 963out_nodev:
964 mutex_unlock(&ft_mutex); 964 mutex_unlock(&ft_mutex);
965 965 return rc;
966 if (rc == -ERESTARTSYS)
967 return restart_syscall();
968 else
969 return rc;
970} 966}
971 967
972/** 968/**