Searched refs:GET_REPLY (Results 1 – 3 of 3) sorted by relevance
| /linux-5.19.10/drivers/media/pci/bt8xx/ |
| D | dst_ca.c | 134 if ((dst_put_ci(state, command, sizeof(command), state->messages, GET_REPLY)) < 0) { in ca_get_app_info()
173 if ((dst_put_ci(state, slot_command, sizeof (slot_command), state->messages, GET_REPLY)) < 0) { in ca_get_ca_info()
217 if ((dst_put_ci(state, slot_command, sizeof (slot_command), slot_cap, GET_REPLY)) < 0) { in ca_get_slot_caps()
257 if ((dst_put_ci(state, slot_command, sizeof (slot_command), slot_info, GET_REPLY)) < 0) { in ca_get_slot_info()
428 if ((ca_set_pmt(state, p_ca_message, hw_buffer, 1, GET_REPLY)) < 0) { in dst_check_ca_pmt()
|
| D | dst_common.h | 77 #define GET_REPLY 1 macro
|
| /linux-5.19.10/Documentation/networking/ |
| D | ethtool-netlink.rst | 267 Kernel replies with corresponding "GET_REPLY" message. For most types, ``GET``
272 layout as corresponding ``GET_REPLY`` is used to request changes. Only
|