Searched refs:replied (Results 1 – 8 of 8) sorted by relevance
698 struct completion replied; member
815 complete(&sync->replied); in dmub_aux_fused_io_callback()2152 init_completion(&adev->dm.fused_io[i].replied); in amdgpu_dm_init()13526 while (wait_for_completion_timeout(&sync->replied, usecs_to_jiffies(timeout_us))) { in execute_fused_io()13527 reinit_completion(&sync->replied); in execute_fused_io()13539 reinit_completion(&sync->replied); in execute_fused_io()
286 echo id to be replied within a CAN_IN_TX_COMPLETE message
1104 When the server received the first SYN, it replied a SYN+ACK, and came into1206 replied an ACK. But kernel handled them in different ways. When the1725 failed, the nstat-b replied an ACK for the first SYN, skipped the ACK
2147 only resolutions for global and link addresses are replied
93 replied to within a second according to the CEC specification,
146 - Wait until this message is replied. If ``reply`` is 0 and the
624 and shouldn't be replied.