/linux/tools/net/ynl/pyynl/ |
H A D | ethtool.py | 43 def print_field(reply, *desc): argument 49 return print_field(reply, *zip(reply.keys(), reply.keys())) 58 value = reply.get(field, None) 94 reply = ynl.dump(op_name, { 'header': {} } | extra) 95 if not reply: 98 for msg in reply: 122 value = bit.get('value', False) 228 reply = dumpit(ynl, args, 'features-get') 229 available = bits_to_dict(reply['hw']) 230 requested = bits_to_dict(reply['wanted']).keys() [all …]
|
H A D | ynl_gen_c.py | 55 self.checks = attr.get('checks', {}) 58 self.reply = False 104 self.reply = True 109 value = self.checks.get(limit, default) 119 value = self.checks.get(limit, default) 126 if const.get('header'): 215 if self.attr.get('byte-order') == 'big-endian': 504 if self.checks.get('unterminated-ok', False): 588 struct_sz = 'sizeof(struct ' + c_lower(self.get("struct")) + ')' 968 self.reply = False [all …]
|
/linux/Documentation/userspace-api/media/dvb/ |
H A D | frontend_fcalls.rst | 14 fe-get-info 16 fe-get-property 19 fe-diseqc-recv-slave-reply
|
/linux/Documentation/networking/ |
H A D | ethtool-netlink.rst | 19 Requests can be divided into three categories: "get" (retrieving information), 23 (``CAP_NET_ADMIN`` in the namespace). Most "get" type requests are allowed for 35 information is not available in "get" requests or value is not to be changed 53 Each request or reply message contains a nested attribute with common header. 75 ``ETHTOOL_FLAG_COMPACT_BITSETS`` use compact format bitsets in reply 76 ``ETHTOOL_FLAG_OMIT_REPLY`` omit optional reply (_SET and _ACT) 103 request) or at least a second request (when the bitset is in a reply). This is 171 In requests, application can use either form. Form used by kernel in reply is 186 ``_GET_REPLY`` kernel reply to a ``GET`` request 187 ``_SET_REPLY`` kernel reply to a ``SET`` request [all …]
|
H A D | nfc.rst | 79 * NFC_CMD_GET_DEVICE - get specific device info or dump the device list 96 sent (including the device id). The user must call GET_TARGET to get the list of 97 all targets found by such device. Each reply message has target attributes with
|
H A D | rxrpc.rst | 61 receives a blob (the reply), and the server receives the request and then 62 transmits the reply. 127 which the service receives; then the service transmits the reply data 155 (#) Reception of a reply data packet implicitly hard-ACK's all the data 158 (#) An call is complete when the request has been sent, the reply has been 159 received and the final hard-ACK on the last packet of the reply has 212 followed by the reply being received with one or more recvmsgs. 235 the reply is transmitted with one or more sendmsgs, and then the final ACK 578 This issues a request_key() to get the key representing the security 615 (6) The reply data will then be posted to the server socket for recvmsg() to [all …]
|
/linux/Documentation/w1/ |
H A D | w1-netlink.rst | 58 W1_CMD_LIST_SLAVES - get slaves list from kernel 76 command request. One reply is generated exactly for one w1_netlink_cmd 77 read request. Replies are not combined when sent - i.e. typical reply 109 reply:: 141 structure) will be 'acked' by the w1 core. Format of the reply is the same 147 If reply is generated for master or root command (which do not have 148 w1_netlink_cmd attached), reply will contain only cn_msg and w1_netlink_msg 157 Status reply is generated for every w1_netlink_cmd embedded in the 159 reply will be generated for the w1_netlink_msg. 176 If command requires reply (like read command) it is sent on command completion. [all …]
|
/linux/drivers/net/ethernet/intel/idpf/ |
H A D | idpf_virtchnl.h | 62 struct kvec reply; member 157 int idpf_send_get_set_rss_key_msg(struct idpf_vport *vport, bool get); 158 int idpf_send_get_set_rss_lut_msg(struct idpf_vport *vport, bool get);
|
/linux/drivers/net/usb/ |
H A D | rndis_host.c | 229 void **reply, int *reply_len) in rndis_query() argument 235 struct rndis_query *get; in rndis_query() member 242 memset(u.get, 0, sizeof *u.get + in_len); in rndis_query() 243 u.get->msg_type = cpu_to_le32(RNDIS_MSG_QUERY); in rndis_query() 244 u.get->msg_len = cpu_to_le32(sizeof *u.get + in_len); in rndis_query() 245 u.get->oid = cpu_to_le32(oid); in rndis_query() 246 u.get->len = cpu_to_le32(in_len); in rndis_query() 247 u.get->offset = cpu_to_le32(20); in rndis_query() 265 *reply = (unsigned char *) &u.get_c->request_id + off; in rndis_query() 299 struct rndis_query *get; in generic_rndis_bind() member
|
/linux/tools/testing/selftests/net/openvswitch/ |
H A D | ovs-dpctl.py | 1869 msgs = self.get() 1936 reply = self.nlm_request( 1939 reply = reply[0] 1942 reply = None 1946 return reply 1979 reply = self.nlm_request( 1982 reply = reply[0] 1985 reply = None 1989 return reply 2000 reply = self.nlm_request( [all …]
|
/linux/Documentation/networking/device_drivers/can/ |
H A D | can327.rst | 170 Once a frame has been sent and wait-for-reply mode is on (``ATR1``, 171 configured on ``listen-only=off``), or when the reply timeout expires 211 "receive reply" mode, in which it *does* ACK any received frames. 213 or the receive reply timeout runs out, the ELM327 will end reply 230 We don't have a way to get real-time notifications on CAN errors. 238 However, they do send ACKs while waiting for a reply immediately 282 The ELM327 will reply with OK when a command is understood, and with ? 304 We need this to be able to get a prompt reliably.
|
/linux/arch/um/drivers/ |
H A D | virtio_uml.c | 359 struct vhost_user_msg reply = { in vhost_user_reply() local 362 size_t size = sizeof(reply.header) + sizeof(reply.payload.integer); in vhost_user_reply() 365 reply.header = msg->header; in vhost_user_reply() 366 reply.header.flags &= ~VHOST_USER_FLAG_NEED_REPLY; in vhost_user_reply() 367 reply.header.flags |= VHOST_USER_FLAG_REPLY; in vhost_user_reply() 368 reply.header.size = sizeof(reply.payload.integer); in vhost_user_reply() 370 rc = full_sendmsg_fds(vu_dev->req_fd, &reply, size, NULL, 0); in vhost_user_reply() 1115 .get = vu_get, 1390 .get = vu_cmdline_get,
|
/linux/drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/r535/ |
H A D | rpc.c | 555 struct nvfw_gsp_rpc *reply; in r535_gsp_rpc_handle_reply() local 562 reply = r535_gsp_msg_recv(gsp, fn, gsp_rpc_len); in r535_gsp_rpc_handle_reply() 563 if (!IS_ERR_OR_NULL(reply)) in r535_gsp_rpc_handle_reply() 564 repv = reply->data; in r535_gsp_rpc_handle_reply() 566 repv = reply; in r535_gsp_rpc_handle_reply() 695 .get = r535_gsp_rpc_get,
|
/linux/tools/testing/selftests/net/netfilter/ |
H A D | nft_nat_zones.sh | 157 ct direction reply meta mark set ct mark 198 … ip netns exec "$gw" nft get element inet raw inicmp "{ 10.1.0.3 . \"veth$i\" . 10.3.0.99 }" 1>&2 203 if ! ip netns exec "$gw" nft get element inet raw inicmp "{ 10.3.0.99 . \"veth0\" . 10.3.0.1 }" | g… 206 ip netns exec "$gw" nft get element inet raw inicmp "{ 10.3.99 . \"veth0\" . 10.3.0.1 }" 1>&2 250 …if ! ip netns exec "$gw" nft get element inet raw inflows "{ 10.1.0.3 . 10000 . \"veth$i\" . 10.3.… 260 if ! ip netns exec "$gw" nft get element inet raw inflows "{ 10.3.0.99 . 5201 . \"veth0\" . 10.3.0.…
|
/linux/net/ceph/ |
H A D | mon_client.c | 587 req->reply); in DEFINE_RB_FUNCS() 590 if (req->reply) in DEFINE_RB_FUNCS() 591 ceph_msg_put(req->reply); in DEFINE_RB_FUNCS() 656 ceph_msg_revoke_incoming(req->reply); in __finish_generic_request() 722 dout("get_generic_reply %lld got %p\n", tid, req->reply); in get_generic_reply() 724 m = ceph_msg_get(req->reply); in get_generic_reply() 742 struct ceph_mon_statfs_reply *reply = msg->front.iov_base; in handle_statfs_reply() local 747 if (msg->front.iov_len != sizeof(*reply)) in handle_statfs_reply() 758 *req->u.st = reply->st; /* struct */ in handle_statfs_reply() 789 req->reply = ceph_msg_new(CEPH_MSG_STATFS_REPLY, 64, GFP_NOFS, true); in ceph_monc_do_statfs() [all …]
|
/linux/Documentation/filesystems/ |
H A D | fuse.rst | 156 or may honor them by sending a reply to the *original* request, with 170 should reply to the INTERRUPT request with an EAGAIN error. In case 172 reply will be ignored. 177 It is possible to get into certain situations where the filesystem is 214 A) mount owner should not be able to get elevated privileges with the 217 B) mount owner should not get illegitimate access to information from 284 filesystem, since *SIGSTOP* can be used to get a similar effect. 331 | [get request from | 405 | | [create reply header before addr]
|
/linux/tools/net/ynl/pyynl/lib/ |
H A D | ynl.py | 329 reply = sock.recv(128 * 1024) 330 nms = NlMsgs(reply) 520 def _recv_dbg_print(self, reply, nl_msgs): argument 523 print("Recv: read", len(reply), "bytes,", 530 if enum.type == 'flags' or attr_spec.get('enum-as-flags', False): 638 if enum.type == 'flags' or attr_spec.get('enum-as-flags', False): 975 reply = self.sock.recv(self._recv_size, socket.MSG_DONTWAIT) 979 nms = NlMsgs(reply) 980 self._recv_dbg_print(reply, nms) 1058 reply = self.sock.recv(self._recv_size) [all …]
|
/linux/Documentation/userspace-api/netlink/ |
H A D | genetlink-legacy.rst | 144 ``reply`` sections of the operations (if an operation has both ``do`` 147 only allocates a ``reply`` (i.e. a "from-kernel" ID). Let's look 158 reply: 246 name: get 291 on how the parsing should be implemented (parse into a single reply
|
H A D | intro.rst | 34 a separate recv() system call is needed to read the reply. 128 (e.g. get information about a netdev). Generic Netlink needs to mux 144 of exchanges to happen, but in practice those are the three that get 238 in reply to ``do`` action requests. In that case the payload is 255 To get information about the Generic Netlink family named for example 289 If the family is found kernel will reply with two messages, the response 292 /* Message #1 - reply */ 448 sockets subscribed to the notifications will get the following message:: 514 means that they may get mixed in with the responses making the message
|
/linux/include/linux/ceph/ |
H A D | messenger.h | 26 struct ceph_connection *(*get)(struct ceph_connection *); member 63 void *reply, int reply_len, 67 u64 global_id, void *reply, int reply_len,
|
/linux/drivers/hid/ |
H A D | hid-steam.c | 448 u8 reply[3 + STEAM_SERIAL_LEN + 1]; in steam_get_serial() local 454 ret = steam_recv_report(steam, reply, sizeof(reply)); in steam_get_serial() 457 if (reply[0] != ID_GET_STRING_ATTRIBUTE || reply[1] < 1 || in steam_get_serial() 458 reply[1] > sizeof(steam->serial_no) || reply[2] != ATTRIB_STR_UNIT_SERIAL) { in steam_get_serial() 462 reply[3 + STEAM_SERIAL_LEN] = 0; in steam_get_serial() 463 strscpy(steam->serial_no, reply + 3, reply[1]); in steam_get_serial() 1845 .get = param_get_bool,
|
/linux/Documentation/admin-guide/ |
H A D | reporting-issues.rst | 98 needs to get reported to the kernel developers separately, unless they are 165 help yourself, if you don't get any help or if it's unsatisfying. 212 might not get the issue solved in older releases: the fix might be too big 213 or risky to get backported there. 262 the fix in the end will get incorporated in all Linux distributions. 323 those often get rejected or ignored, so consider yourself warned. But it's still 325 indirectly will help to get the issue fixed over time. 348 If you get flooded with results consider telling your search engine to limit 365 details on how to get properly involved. 385 fixed as soon as possible, hence there are 'issues of high priority' that get [all …]
|
/linux/drivers/net/wireless/ath/wil6210/ |
H A D | main.c | 67 .get = param_get_uint, 96 .get = param_get_uint, 470 } __packed reply; in wil_disconnect_worker() local 480 memset(&reply, 0, sizeof(reply)); in wil_disconnect_worker() 483 WMI_DISCONNECT_EVENTID, &reply, sizeof(reply), in wil_disconnect_worker()
|
/linux/drivers/platform/cznic/ |
H A D | turris-omnia-mcu-gpio.c | 780 u8 reply[OMNIA_CMD_INT_ARG_LEN] = {}; in omnia_irq_read_pending_new() local 792 err = omnia_cmd_read(mcu->client, OMNIA_CMD_GET_INT_AND_CLEAR, reply, in omnia_irq_read_pending_new() 800 omnia_mask_deinterleave(reply, &rising, &falling); in omnia_irq_read_pending_new() 1025 mcu->gc.get = omnia_gpio_get; in omnia_mcu_register_gpiochip()
|
/linux/Documentation/watchdog/ |
H A D | watchdog-api.rst | 133 There is also a get function for getting the pretimeout:: 221 WDIOF_KEEPALIVEPING Keep alive ping reply 227 WDIOF_SETTIMEOUT Can set/get the timeout 233 WDIOF_PRETIMEOUT Pretimeout (in seconds), get/set
|