Home
last modified time | relevance | path

Searched +refs:get +refs:reply (Results 1 – 25 of 56) sorted by relevance

123

/Linux-v6.6/tools/net/ynl/
Dethtool.py39 def print_field(reply, *desc): argument
45 return print_field(reply, *zip(reply.keys(), reply.keys()))
54 value = reply.get(field, None)
90 reply = ynl.dump(op_name, { 'header': {} } | extra)
91 if not reply:
94 for msg in reply:
118 value = bit.get('value', False)
223 reply = dumpit(ynl, args, 'features-get')
224 available = bits_to_dict(reply['hw'])
225 requested = bits_to_dict(reply['wanted']).keys()
[all …]
Dynl-gen-c.py43 self.checks = attr.get('checks', {})
365 if self.checks.get('unterminated-ok', False):
614 self.reply = False
680 self.value_pfx = yaml.get('name-prefix', f"{family.name}-{yaml['name']}-")
709 self.max_name = c_upper(self.yaml.get('attr-max-name', f"{self.name_prefix}max"))
798 self.fam_key = c_upper(self.yaml.get('c-family-name', self.yaml["name"] + '_FAMILY_NAME'))
799 … self.ver_key = c_upper(self.yaml.get('c-version-name', self.yaml["name"] + '_FAMILY_VERSION'))
812 … if self.yaml.get('protocol', 'genetlink') not in {'genetlink', 'genetlink-c', 'genetlink-legacy'}:
825 self.mcgrps = self.yaml.get('mcast-groups', {'list': []})
847 self.kernel_policy = self.yaml.get('kernel-policy', 'split')
[all …]
/Linux-v6.6/Documentation/userspace-api/media/dvb/
Dfrontend_fcalls.rst14 fe-get-info
16 fe-get-property
19 fe-diseqc-recv-slave-reply
/Linux-v6.6/Documentation/networking/
Dethtool-netlink.rst19 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.
74 ``ETHTOOL_FLAG_COMPACT_BITSETS`` use compact format bitsets in reply
75 ``ETHTOOL_FLAG_OMIT_REPLY`` omit optional reply (_SET and _ACT)
96 request) or at least a second request (when the bitset is in a reply). This is
164 In requests, application can use either form. Form used by kernel in reply is
179 ``_GET_REPLY`` kernel reply to a ``GET`` request
180 ``_SET_REPLY`` kernel reply to a ``SET`` request
[all …]
Dnfc.rst79 * 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
Drxrpc.rst61 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-v6.6/Documentation/w1/
Dw1-netlink.rst58 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-v6.6/drivers/net/usb/
Drndis_host.c229 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-v6.6/tools/testing/selftests/net/openvswitch/
Dovs-dpctl.py1424 msgs = self.get()
1491 reply = self.nlm_request(
1494 reply = reply[0]
1497 reply = None
1501 return reply
1534 reply = self.nlm_request(
1537 reply = reply[0]
1540 reply = None
1544 return reply
1555 reply = self.nlm_request(
[all …]
/Linux-v6.6/Documentation/networking/device_drivers/can/
Dcan327.rst170 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-v6.6/arch/um/drivers/
Dvirtio_uml.c349 struct vhost_user_msg reply = { in vhost_user_reply() local
352 size_t size = sizeof(reply.header) + sizeof(reply.payload.integer); in vhost_user_reply()
355 reply.header = msg->header; in vhost_user_reply()
356 reply.header.flags &= ~VHOST_USER_FLAG_NEED_REPLY; in vhost_user_reply()
357 reply.header.flags |= VHOST_USER_FLAG_REPLY; in vhost_user_reply()
358 reply.header.size = sizeof(reply.payload.integer); in vhost_user_reply()
360 rc = full_sendmsg_fds(vu_dev->req_fd, &reply, size, NULL, 0); in vhost_user_reply()
1095 .get = vu_get,
1370 .get = vu_cmdline_get,
/Linux-v6.6/Documentation/userspace-api/netlink/
Dgenetlink-legacy.rst120 ``reply`` sections of the operations (if an operation has both ``do``
123 only allocates a ``reply`` (i.e. a "from-kernel" ID). Let's look
134 reply:
222 name: get
267 on how the parsing should be implemented (parse into a single reply
Dintro.rst34 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
251 To get information about the Generic Netlink family named for example
285 If the family is found kernel will reply with two messages, the response
288 /* Message #1 - reply */
444 sockets subscribed to the notifications will get the following message::
510 means that they may get mixed in with the responses making the message
/Linux-v6.6/net/ceph/
Dmon_client.c587 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-v6.6/Documentation/filesystems/
Dfuse.rst156 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-v6.6/tools/testing/selftests/netfilter/
Dnft_nat_zones.sh202 ct direction reply meta mark set ct mark
244 ip netns exec $gw nft get element inet raw inicmp "{ 10.1.0.3 . \"veth$i\" . 10.3.0.99 }" 1>&2
249 ip netns exec $gw nft get element inet raw inicmp "{ 10.3.0.99 . \"veth0\" . 10.3.0.1 }" | grep -q …
253 ip netns exec $gw nft get element inet raw inicmp "{ 10.3.99 . \"veth0\" . 10.3.0.1 }" 1>&2
292 …ip netns exec $gw nft get element inet raw inflows "{ 10.1.0.3 . 10000 . \"veth$i\" . 10.3.0.99 . …
303 ip netns exec $gw nft get element inet raw inflows "{ 10.3.0.99 . 5201 . \"veth0\" . 10.3.0.1 . 100…
/Linux-v6.6/drivers/hid/
Dhid-steam.c272 u8 reply[3 + STEAM_SERIAL_LEN + 1]; in steam_get_serial() local
277 ret = steam_recv_report(steam, reply, sizeof(reply)); in steam_get_serial()
280 if (reply[0] != 0xae || reply[1] != 0x15 || reply[2] != 0x01) in steam_get_serial()
282 reply[3 + STEAM_SERIAL_LEN] = 0; in steam_get_serial()
283 strscpy(steam->serial_no, reply + 3, sizeof(steam->serial_no)); in steam_get_serial()
1453 .get = param_get_bool,
/Linux-v6.6/net/vmw_vsock/
Dvirtio_transport.c106 bool reply; in virtio_transport_send_pkt_work() local
113 reply = virtio_vsock_skb_reply(skb); in virtio_transport_send_pkt_work()
131 if (reply) { in virtio_transport_send_pkt_work()
340 vdev->config->get(vdev, offsetof(struct virtio_vsock_config, guest_cid), in virtio_vsock_update_guest_cid()
/Linux-v6.6/include/linux/ceph/
Dmessenger.h26 struct ceph_connection *(*get)(struct ceph_connection *); member
63 void *reply, int reply_len,
67 u64 global_id, void *reply, int reply_len,
/Linux-v6.6/Documentation/admin-guide/
Dreporting-issues.rst98 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-v6.6/drivers/net/wireless/ath/wil6210/
Dmain.c67 .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-v6.6/Documentation/watchdog/
Dwatchdog-api.rst133 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
/Linux-v6.6/net/netfilter/ipvs/
Dip_vs_ctl.c2865 const struct ip_vs_get_services *get, in __ip_vs_get_service_entries() argument
2879 if (count >= get->num_services) in __ip_vs_get_service_entries()
2898 if (count >= get->num_services) in __ip_vs_get_service_entries()
2915 __ip_vs_get_dest_entries(struct netns_ipvs *ipvs, const struct ip_vs_get_dests *get, in __ip_vs_get_dest_entries() argument
2919 union nf_inet_addr addr = { .ip = get->addr }; in __ip_vs_get_dest_entries()
2923 if (get->fwmark) in __ip_vs_get_dest_entries()
2924 svc = __ip_vs_svc_fwm_find(ipvs, AF_INET, get->fwmark); in __ip_vs_get_dest_entries()
2926 svc = __ip_vs_service_find(ipvs, AF_INET, get->protocol, &addr, in __ip_vs_get_dest_entries()
2927 get->port); in __ip_vs_get_dest_entries()
2938 if (count >= get->num_dests) in __ip_vs_get_dest_entries()
[all …]
/Linux-v6.6/Documentation/process/
Dhandling-regressions.rst30 introduced v5.13..v5.14-rc1``. If not, send a reply (with the regressions
70 try to ensure it gets CCed again in case you reply to a reply that omitted
82 ``#regzbot introduced 1f2e3d4c5b6a``. If not, send a reply (with the
92 parent mail (the one you reply to) as the initial report for the regression
246 to account for the time it takes to get fixes tested, reviewed, and merged by
397 By using a 'regzbot command' in a direct or indirect reply to the mail with the
410 or itself is a reply to that mail:
516 But if something actually breaks, then the change must get fixed or
635 they get found, they get fixed, and it has nothing to do with "we
697 And regressions get reverted, unless there are security issues or
/Linux-v6.6/drivers/message/fusion/lsi/
Dmpi_history.txt119 * 12-04-00 01.01.02 Modified IOCFacts reply, added FWUpload messages, and
123 * Added ImageType to FwUpload reply.
155 * the IOCFacts reply.
156 * Added two new PortTypes for the PortFacts reply.
191 * Added MaxInitiators field to PortFacts reply.
596 * 03-14-02 01.02.05 Modified MPI_TARGET_FCP_RSP_BUFFER to get the proper
628 * 01-25-01 01.01.04 Move InitiatorIndex in LinkServiceRsp reply to a larger
681 * 07-12-02 01.02.07 Added structures for Mailbox request and reply.
724 * reply.

123