Searched refs:NLM_F_ACK (Results 1 – 15 of 15) sorted by relevance
74 .nlmsg_flags = NLM_F_REQUEST | NLM_F_ACK, in tst_crypto_add_alg()92 .nlmsg_flags = NLM_F_REQUEST | NLM_F_ACK, in tst_crypto_del_alg()
371 if (!(msg->nlmsg_flags & NLM_F_ACK)) in tst_rtnl_check_acks()
24 .nlmsg_flags = NLM_F_REQUEST | NLM_F_ACK | flags, in create_request()
78 #define NLM_F_ACK 4
17 #define NLM_F_ACK 4 macro
56 #define NLM_F_ACK 0x04 /* Reply with ack, with zero or error code */ macro
382 NLM_F_ACK | NLM_F_REQUEST); in osf_load_line()385 NLM_F_ACK | NLM_F_REQUEST | NLM_F_CREATE); in osf_load_line()
367 validates results of requests sent with the +NLM_F_ACK+ flag. This function385 *response)+ – Validate results of requests sent with the +NLM_F_ACK+ flag.388 result validation. Returns 1 if all messages sent with the +NLM_F_ACK+ flag453 .nlmsg_flags = NLM_F_REQUEST | NLM_F_ACK | NLM_F_CREATE |
499 nlh->nlmsg_flags |= NLM_F_ACK; in nl_complete_msg()924 if (hdr->nlmsg_flags & NLM_F_ACK) { in recvmsgs()
385 flags = NLM_F_ACK; in fetch_set_cache()433 c ? NLM_F_ACK : NLM_F_DUMP, h->seq); in __fetch_chain_cache()
3210 nlh->nlmsg_flags = NLM_F_REQUEST | NLM_F_ACK; in nft_compatible_revision()
628 request.mhdr.nlmsg_flags = NLM_F_REQUEST|NLM_F_ACK; in linkupdate()969 request.mhdr.nlmsg_flags = NLM_F_REQUEST|NLM_F_ACK; in link_show()1125 req.nlm.nlmsg_flags = NLM_F_REQUEST|NLM_F_ACK; in ipaddrupdate()1725 mhdr->nlmsg_flags = NLM_F_REQUEST | NLM_F_ACK; in display_route_info()1792 request.mhdr.nlmsg_flags = NLM_F_REQUEST | NLM_F_ACK; in route_get()1860 mhdr->nlmsg_flags = NLM_F_REQUEST | NLM_F_ACK; in route_get()2024 req.hdr.nlmsg_flags = NLM_F_ACK| NLM_F_REQUEST | route_flags; in route_update()2200 request.mhdr.nlmsg_flags = NLM_F_REQUEST | NLM_F_ACK | in ruleupdate()
207 nlh->nlmsg_flags = NLM_F_ACK; in rtnl_route()
395 A=>B [label="MSG_SETCFG (seq=1, NLM_F_REQUEST, NLM_F_ACK)"];469 processed by setting the +NLM_F_ACK+ flag in the request. This is typically477 A=>B [label="GET (seq=1, NLM_F_REQUEST | NLM_F_ACK)"];494 #define NLM_F_ACK 4500 - `NLM_F_ACK` - ACK message requested, see <<core_msg_ack>>.503 The flag +NLM_F_ECHO+ is similar to the `NLM_F_ACK` flag. It can be1161 message has the NLM_F_ACK flag set. Although I am not aware of any1180 | Message has NLM_F_ACK set2513 | NL_CB_SEND_ACK | Messages with NLM_F_ACK flag set | NL_OK
82 NLM_F_ACK = 4 variable