Searched refs:unblock (Results 1 – 9 of 9) sorted by relevance
47 API-scsi-internal-device-unblock111 API-iscsi-unblock-session
84 API-posix-unblock-lock
715 API-disk-unblock-events
62 By default, the driver expects the patches for block/unblock interfaces
346 Convert to using block/unblock on list remove (was del/add)574 unblock (stop dev_loss_tmo) when appopriate.593 context. It seems to be not nessasery to unblock target from626 for 2.6.5 kernel with block/unblock patch.641 target_block/unblock only if FC_TRANS_VER1.645 block/unblock. This member allows the driver to know when to646 unblock for pci_remove_one or pci_add_one. #ifdef'd some more647 block/unblock stuff and removed some defensive checks from648 target_block/unblock.651 * Removed NULL target check from target_block/unblock and fixed up[all …]
686 * @shost: pointer to host to unblock commands on
738 bool unblock = false; in sbp2_conditionally_unblock() local743 unblock = --tgt->blocked == 0; in sbp2_conditionally_unblock()747 if (unblock) in sbp2_conditionally_unblock()
232 HCI Responses are dispatched immediately from this context to unblock
359 void (*lm_notify)(struct file_lock *); /* unblock callback */