Searched refs:CRYPTO_RESP (Results 1 – 4 of 4) sorted by relevance
440 if (code & CRYPTO_RESP) { in crypto_recv()483 temp32 = CRYPTO_RESP; in crypto_recv()488 case CRYPTO_ASSOC | CRYPTO_RESP: in crypto_recv()597 case CRYPTO_CERT | CRYPTO_RESP: in crypto_recv()667 case CRYPTO_IFF | CRYPTO_RESP: in crypto_recv()715 case CRYPTO_GQ | CRYPTO_RESP: in crypto_recv()756 case CRYPTO_MV | CRYPTO_RESP: in crypto_recv()819 temp32 = CRYPTO_RESP; in crypto_recv()854 case CRYPTO_COOK | CRYPTO_RESP: in crypto_recv()936 case CRYPTO_AUTO | CRYPTO_RESP: in crypto_recv()[all …]
2553 CRYPTO_RESP, NULL);2556 CRYPTO_RESP, NULL);2615 CRYPTO_RESP, NULL);2970 temp32 = CRYPTO_RESP;
56 #define CRYPTO_RESP 0x80000000 /* response */ macro
1030 CRYPTO_ASSOC and CRYPTO_RESP packets, and in other places.1032 CRYPTO_RESP packets. Use FLAG_ASSOC, not CRYPTO_FLAG_ASSOC. More2374 CRYPTO_RESP and reorder the update of tstamp.