Searched refs:NAK (Results 1 – 10 of 10) sorted by relevance
43 到的是NAK回复。回复需要几天的时间，这取决于开发者的时间安排。53 - 审查委员会有48小时的时间，用来决定给该补丁回复ACK还是NAK。
56 には NAK を受け取る。この反応は開発者たちのスケジュールによって、数70 - レビュー委員会は 48時間の間に ACK か NAK を出す。
434 put_char(pInfo, NAK); in retry_transmit()504 put_char(pInfo, NAK); in on_receive_block()586 if (c == NAK) { in receive_char()707 put_char(pInfo, NAK); in on_timeout()717 put_char(pInfo, NAK); in on_timeout()724 put_char(pInfo, NAK); in on_timeout()734 put_char(pInfo, NAK); in on_timeout()
60 #define NAK 0x15 macro
436 NAK = (1U << 14), /* NAK rx'd */ enumerator
143 queue, or a NAK if the patch is rejected. This response might take a few156 - The review committee has 48 hours in which to ACK or NAK the patch.
99 #define NAK 0x15 macro517 } else if (data == NAK) { in gsp_receive()518 ack_or_nak_seen = NAK; in gsp_receive()
33 current frame. A NAK indicates that the command was in error and will not
155 coda, oppure un NAK se la patch è stata rigettata. A seconda degli impegni
366 #define NAK 2 /* Negative acknowledgement to PC driver */ macro949 while (mbval > NAK) { in fst_issue_cmd()964 if (mbval == NAK) { in fst_issue_cmd()
