| /Linux-v6.6/Documentation/userspace-api/media/dvb/ |
| D | frontend_fcalls.rst | 14 fe-get-info
16 fe-get-property
19 fe-diseqc-recv-slave-reply
|
| /Linux-v6.6/Documentation/networking/ |
| 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.
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 …]
|
| 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
|
| D | ip-sysctl.rst | 73 Controls the fwmark of kernel-generated IPv4 reply packets that are not
856 get detected right after Fastopen is re-enabled and will reset to
1530 - 1 - Enforce to use IGMP version 1. Will also reply IGMPv1 report if
1533 IGMPv1 query message. Will reply report if receive IGMPv3 query.
1629 will be chosen, setting to zero means reply with no delay.
1779 with the hope we will receive reply for our request and
1792 - 0 - (default): reply for any local target IP address, configured
1794 - 1 - reply only if the target IP address is local address
1796 - 2 - reply only if the target IP address is local address
1799 - 3 - do not reply for local addresses configured with scope host,
[all …]
|
| D | can.rst | 276 /* transport protocol class address info (e.g. ISOTP) */
368 /* get interface name of the received CAN frame */
671 socket option returns an error: No problem. You'll get Classical CAN frames
878 Send reply for RTR-request (placed in op->frames[0]).
934 CAN frame is stateless as state changes within the ival2 period may get
1228 Netlink interface to set/get devices properties
1288 More info to the above output:
1472 Please check the "Kconfig" file in "drivers/net/can" to get an actual
|
| D | arcnet-hardware.rst | 27 First of all, you can get ARCnet cards in at least two speeds: 2.5 Mbps
45 Once you get past these little stumbling blocks, ARCnet is actually quite a
450 - And some other stuff (more info is welcome!)::
989 Note: this data is gathered by experimenting and looking at info of other
1269 way, you get contiguous high memory from 0xD100 almost all the way
1707 the time I tried to reach him. Sorry Vlad, if you didn't get my reply.
2390 In a chip Socket with info printed on a label covering a round window
3230 send any and all info to:
|
| /Linux-v6.6/drivers/net/usb/ |
| D | rndis_host.c | 60 struct cdc_state *info = (void *)&dev->data; in rndis_msg_indicate() local
61 struct device *udev = &info->control->dev; in rndis_msg_indicate()
93 struct cdc_state *info = (void *) &dev->data; in rndis_command() local
115 master_ifnum = info->control->cur_altsetting->desc.bInterfaceNumber; in rndis_command()
162 dev_dbg(&info->control->dev, in rndis_command()
167 dev_dbg(&info->control->dev, in rndis_command()
189 dev_dbg(&info->control->dev, in rndis_command()
195 dev_dbg(&info->control->dev, in rndis_command()
201 dev_dbg(&info->control->dev, in rndis_command()
206 dev_dbg(&info->control->dev, "rndis response timeout\n"); in rndis_command()
[all …]
|
| /Linux-v6.6/arch/um/drivers/ |
| D | virtio_uml.c | 349 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()
779 struct virtio_uml_vq_info *info = vq->priv; in vu_notify() local
783 if (info->suspended) in vu_notify()
788 if (info->kick_fd < 0) { in vu_notify()
[all …]
|
| /Linux-v6.6/tools/testing/selftests/net/openvswitch/ |
| D | ovs-dpctl.py | 1424 msgs = self.get()
1482 def info(self, dpname, ifindex=0): member in OvsDatapath
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
[all …]
|
| /Linux-v6.6/fs/ceph/ |
| D | mds_client.c | 75 struct ceph_mds_reply_info_in *info) in parse_reply_info_quota() argument
89 ceph_decode_64_safe(p, end, info->max_bytes, bad); in parse_reply_info_quota()
90 ceph_decode_64_safe(p, end, info->max_files, bad); in parse_reply_info_quota()
101 struct ceph_mds_reply_info_in *info, in parse_reply_info_in() argument
122 info->in = *p; in parse_reply_info_in()
124 sizeof(*info->in->fragtree.splits) * in parse_reply_info_in()
125 le32_to_cpu(info->in->fragtree.nsplits); in parse_reply_info_in()
127 ceph_decode_32_safe(p, end, info->symlink_len, bad); in parse_reply_info_in()
128 ceph_decode_need(p, end, info->symlink_len, bad); in parse_reply_info_in()
129 info->symlink = *p; in parse_reply_info_in()
[all …]
|
| /Linux-v6.6/net/netfilter/ipvs/ |
| D | ip_vs_ctl.c | 2865 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/sound/pci/hda/ |
| D | patch_ca0132.c | 2359 unsigned int len, void *reply, unsigned int *reply_len) in dspio_scp() argument
2373 if (dir == SCP_GET && reply == NULL) { in dspio_scp()
2378 if (reply != NULL && (reply_len == NULL || (*reply_len == 0))) { in dspio_scp()
2421 } else if (!reply) { in dspio_scp()
2426 memcpy(reply, scp_reply.data, *reply_len); in dspio_scp()
3920 static unsigned int ca0132_playback_pcm_delay(struct hda_pcm_stream *info, in ca0132_playback_pcm_delay() argument
4011 static unsigned int ca0132_capture_pcm_delay(struct hda_pcm_stream *info, in ca0132_capture_pcm_delay() argument
4042 .info = ca0132_volume_info, \
4043 .get = ca0132_volume_get, \
4060 .info = snd_hda_mixer_amp_volume_info, \
[all …]
|
| /Linux-v6.6/drivers/net/wireless/ath/wil6210/ |
| 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()
1458 struct cfg80211_scan_info info = { in wil_abort_scan() local
1478 cfg80211_scan_done(vif->scan_request, &info); in wil_abort_scan()
|
| /Linux-v6.6/Documentation/process/ |
| D | handling-regressions.rst | 30 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
300 CCing the Linux kernel's regression tracker (regressions@leemhuis.info); if the
366 Check `regzbot's web-interface <https://linux-regtracking.leemhuis.info/regzbot/>`_
367 for the latest info; alternatively, `search for the latest regression report
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:
[all …]
|
| D | howto.rst | 46 definitive reference for them. Please check the gcc info pages (`info
155 happen, and what to do if you want to get a change into one of these
358 Fixing bugs is one of the best ways to get merits among other developers,
362 Check the MAINTAINERS file where bugs for that subsystem get reported to; often
367 kernel get filed there.
406 get pretty large. Don't remove anybody from the CC: list without a good
407 reason, or don't reply only to the list address. Get used to receiving the
412 keep the "John Kernelhacker wrote ...:" lines at the top of your reply, and
423 own patch by yourself. If that doesn't work, get your mail program fixed
448 again, sometimes things get lost in the huge volume.
[all …]
|
| D | maintainer-kvm-x86.rst | 68 especially for the current release and or stable trees, get to jump the queue.
76 Pings to get a status update are welcome, but keep in mind the timing of the
205 is arguably the most important information, and so that info should be easy to
223 preference. E.g. having to skip one sentence to get to the context is less
224 painful than having to skip three paragraphs to get to "what's changing".
235 do get backported, but require explicit maintainer approval (search MANUALSEL).
289 Posting new feature development without tests to get early feedback is more
355 know that KVM-unit-tests is a separate repository and get confused when patches
363 in reply to the original posting (cover letter for multi-patch series). The
372 If for some reason a patch is dropped after officially being accepted, a reply
|
| D | submitting-patches.rst | 81 Solve only one problem per patch. If your description starts to get
207 the reviewers time and will get your patch rejected, probably
260 to allow distributors to get the patch out to users; in such cases,
315 Your patch will almost certainly get comments from reviewers on ways in
316 which the patch can be improved, in the form of a reply to your email. You must
317 respond to those comments; ignoring reviewers is a good way to get ignored in
318 return. You can simply reply to their emails to answer their comments. Review
325 reviewers sometimes get grumpy. Even in that case, though, respond
346 Q: Were do I find info about this thing called top-posting?
353 to your reply. This makes responses easier to find, and saves time and
[all …]
|
| /Linux-v6.6/Documentation/admin-guide/ |
| 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 …]
|
| D | reporting-regressions.rst | 83 `regzbot's web-interface <https://linux-regtracking.leemhuis.info/regzbot/>`_.
129 kernel regressions <https://linux-regtracking.leemhuis.info/regzbot/>`_ and the
168 CCing the Linux kernel's regression tracker (regressions@leemhuis.info); if the
215 get it tracked immediately.
387 Check out `regzbot's web-interface <https://linux-regtracking.leemhuis.info/regzbot/>`_.
400 By using a 'regzbot command' in a direct or indirect reply to the mail with the
402 mailing list archive and reply to it using your mailer's "Reply-all" function.
|
| /Linux-v6.6/drivers/gpu/drm/bridge/ |
| D | ti-sn65dsi86.c | 558 msg->reply = 0; in ti_sn_aux_transfer()
610 msg->reply |= DP_AUX_I2C_REPLY_NACK; in ti_sn_aux_transfer()
614 msg->reply |= DP_AUX_NATIVE_REPLY_NACK; in ti_sn_aux_transfer()
701 const struct mipi_dsi_device_info info = { .type = "ti_sn_bridge", in ti_sn_attach_host() local
710 dsi = devm_mipi_dsi_device_register_full(&adev->dev, host, &info); in ti_sn_attach_host()
779 const struct drm_display_info *info, in ti_sn_bridge_mode_valid() argument
1820 pdata->gchip.get = ti_sn_bridge_gpio_get; in ti_sn_gpio_probe()
|
| /Linux-v6.6/Documentation/networking/device_drivers/ethernet/marvell/ |
| D | octeontx2.rst | 90 - NPC parser profile config, basically how to parse pkt and what info to extract.
107 links this driver talks to AF and AF gets that info from firmware and responds
123 the reply to VF.
149 3. Then submitted to NPC block for parsing and then MCAM lookup to get the destination RVU device.
|
| /Linux-v6.6/Documentation/scsi/ |
| D | ChangeLog.megaraid_sas | 122 8. Add multiple MSI-X vector/multiple reply queue support.
218 d). in Driver's ISR routine, if driver get the FW state as
252 3. driver fixed the device update issue after get the AEN
284 2. Add the fix of deallocating memory after get pdlist.
348 1. Rollback the sense info implementation
398 FW. Prior versions calculated this value from controller info
403 duplication steps that helped to get to the root cause of the
|
| /Linux-v6.6/Documentation/sound/ |
| D | alsa-configuration.rst | 1092 matches with your device, report it together with alsa-info.sh
1099 Note 2: If you get click noises on output, try the module option
1112 NB: If you get many ``azx_get_response timeout`` messages at
1118 single command mode is provided only for BIOS, and you won't get
2134 my guest. Remember, the idea is to get a number that causes us
2141 How long to sleep when waiting for reply (default: 100)
2162 Copy (or symlink) the file appropriately if you get an error
2314 NB: ``ignore_ctl_error=1`` may help when you get an error at accessing
2765 alsa-info.sh script
2766 https://www.alsa-project.org/alsa-info.sh
|
