Searched refs:unblock (Results 1 – 6 of 6) sorted by relevance
693 bool unblock = false; in bd_end_claim() local709 unblock = true; in bd_end_claim()719 if (unblock) { in bd_end_claim()
60 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 appropriate.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 …]
61 FRED allows explicit unblock of NMI with new event return instructions
727 bool unblock = false; in sbp2_conditionally_unblock() local732 unblock = --tgt->blocked == 0; in sbp2_conditionally_unblock()736 if (unblock) in sbp2_conditionally_unblock()
252 HCI Responses are dispatched immediately from this context to unblock