Searched refs:NAK (Results 1 – 9 of 9) sorted by relevance
47 到的是NAK回复。回复需要几天的时间，这取决于开发者的时间安排。56 - 审查委员会有48小时的时间，用来决定给该补丁回复ACK还是NAK。
56 には NAK を受け取る。この反応は開発者たちのスケジュールによって、数70 - レビュー委員会は 48時間の間に ACK か NAK を出す。
427 put_char(pInfo, NAK); in retry_transmit()497 put_char(pInfo, NAK); in on_receive_block()579 if (c == NAK) { in receive_char()701 put_char(pInfo, NAK); in on_timeout()711 put_char(pInfo, NAK); in on_timeout()718 put_char(pInfo, NAK); in on_timeout()728 put_char(pInfo, NAK); in on_timeout()
60 #define NAK 0x15 macro
452 NAK = (1U << 14), /* NAK rx'd */ enumerator
140 queue, or a NAK if the patch is rejected. This response might take a few153 - The review committee has 48 hours in which to ACK or NAK the patch.
99 #define NAK 0x15 macro514 } else if (data == NAK) { in gsp_receive()515 ack_or_nak_seen = NAK; in gsp_receive()
33 current frame. A NAK indicates that the command was in error and will not
370 #define NAK 2 /* Negative acknowledgement to PC driver */ macro953 while (mbval > NAK) { in fst_issue_cmd()968 if (mbval == NAK) { in fst_issue_cmd()
