| /linux-6.14.4/Documentation/ABI/testing/ |
| D | configfs-iio | 20 High resolution timers directory. Creating a directory here
21 will result in creating a hrtimer trigger in the IIO subsystem.
33 Dummy IIO devices directory. Creating a directory here will result
34 in creating a dummy IIO device in the IIO subsystem.
|
| /linux-6.14.4/Documentation/usb/ |
| D | gadget-testing.rst | 41 The function name to use when creating the function directory is "acm".
80 The function name to use when creating the function directory is "ecm".
93 and after creating the functions/ecm.<instance name> they contain default
120 The function name to use when creating the function directory is "geth".
133 and after creating the functions/ecm.<instance name> they contain default
160 The function name to use when creating the function directory is "eem".
173 and after creating the functions/eem.<instance name> they contain default
200 The function name to use when creating the function directory is "ffs".
203 After creating the directory there is a new instance (a "device") of FunctionFS
232 The function name to use when creating the function directory is "hid".
[all …]
|
| D | gadget_configfs.rst | 24 Creating a gadget means deciding what configurations there will be
59 1. Creating the gadgets
103 2. Creating the configurations
133 3. Creating the functions
162 creating symbolic links::
|
| /linux-6.14.4/drivers/net/ethernet/mellanox/mlx5/core/steering/sws/ |
| D | dr_fw.c | 29 mlx5dr_err(dmn, "Failed creating TTL W/A FW flow table %d\n", ret); in mlx5dr_fw_create_recalc_cs_ft()
37 mlx5dr_err(dmn, "Failed creating TTL W/A FW flow group %d\n", ret); in mlx5dr_fw_create_recalc_cs_ft()
124 mlx5dr_err(dmn, "Failed creating multi dest FW flow table %d\n", ret); in mlx5dr_fw_create_md_tbl()
132 mlx5dr_err(dmn, "Failed creating multi dest FW flow group %d\n", ret); in mlx5dr_fw_create_md_tbl()
|
| /linux-6.14.4/tools/testing/selftests/kvm/x86/ |
| D | max_vcpuid_cap_test.c | 49 TEST_ASSERT(ret < 0, "Creating vCPU with ID > MAX_VCPU_ID should fail"); in main()
53 TEST_ASSERT(ret < 0, "Creating vCPU with ID[63:32] != 0 should fail"); in main()
57 TEST_ASSERT(ret >= 0, "Creating vCPU with ID 0 should succeed"); in main()
|
| /linux-6.14.4/Documentation/userspace-api/ |
| D | unshare.rst | 48 shared resources without creating a new process. unshare() is a natural
56 where creating a new process to control sharing/unsharing of process
58 when creating a new process using fork or clone, unshare() can benefit
83 client requests by creating processes that share resources such as
85 decide what needs to be shared at the time of creating the process
139 shared by explicit request to share them when creating a process
143 shared execution context without creating a new process.
|
| D | lsm.rst | 31 creating file system objects.
36 creating key objects.
47 creating socket objects.
|
| /linux-6.14.4/drivers/net/wireless/broadcom/brcm80211/brcmfmac/ |
| D | fwil.c | 208 bphy_err(drvr, "Creating iovar failed\n"); in brcmf_fil_iovar_data_set()
235 bphy_err(drvr, "Creating iovar failed\n"); in brcmf_fil_iovar_data_get()
315 bphy_err(drvr, "Creating bsscfg failed\n"); in brcmf_fil_bsscfg_data_set()
342 bphy_err(drvr, "Creating bsscfg failed\n"); in brcmf_fil_bsscfg_data_get()
396 bphy_err(drvr, "Creating xtlv failed\n"); in brcmf_fil_xtlv_data_set()
422 bphy_err(drvr, "Creating bsscfg failed\n"); in brcmf_fil_xtlv_data_get()
|
| /linux-6.14.4/Documentation/networking/device_drivers/wwan/ |
| D | iosm.rst | 70 traffic. Iproute network utility is used for creating "wwan0-X" network
74 The userspace management application is responsible for creating new IP link
77 For example, creating new IP link for a MBIM IP session with SessionId 1:
|
| /linux-6.14.4/Documentation/admin-guide/cgroup-v1/ |
| D | net_cls.rst | 13 Creating a net_cls cgroups instance creates a net_cls.classid file.
38 - creating traffic class 10:1::
|
| /linux-6.14.4/drivers/net/ethernet/mellanox/mlx5/core/en/ |
| D | htb.c | 320 NL_SET_ERR_MSG_MOD(extack, "Firmware error when creating a leaf node."); in mlx5e_htb_leaf_alloc_queue()
330 NL_SET_ERR_MSG_MOD(extack, "Error creating an SQ."); in mlx5e_htb_leaf_alloc_queue()
362 NL_SET_ERR_MSG_MOD(extack, "Firmware error when creating an inner node."); in mlx5e_htb_leaf_to_inner()
382 NL_SET_ERR_MSG_MOD(extack, "Firmware error when creating a leaf node."); in mlx5e_htb_leaf_to_inner()
409 NL_SET_ERR_MSG_MOD(extack, "Error creating an SQ."); in mlx5e_htb_leaf_to_inner()
523 NL_SET_ERR_MSG_MOD(extack, "Error creating an SQ."); in mlx5e_htb_leaf_del()
561 NL_SET_ERR_MSG_MOD(extack, "Firmware error when creating a leaf node."); in mlx5e_htb_leaf_del_last()
605 NL_SET_ERR_MSG_MOD(extack, "Error creating an SQ."); in mlx5e_htb_leaf_del_last()
|
| /linux-6.14.4/Documentation/admin-guide/device-mapper/ |
| D | zero.rst | 11 One very interesting use of dm-zero is for creating "sparse" devices in
20 To create a sparse device, start by creating a dm-zero device that's the
|
| D | thin-provisioning.rst | 83 to 2MB if the answer is smaller. If you're creating large numbers of
160 i) Creating a new thinly-provisioned volume.
182 i) Creating an internal snapshot.
187 must suspend it before creating the snapshot to avoid corruption.
229 i) Creating a snapshot of an external device
231 This is the same as creating a thin device.
|
| /linux-6.14.4/fs/sysfs/ |
| D | symlink.c | 57 * @kn: directory we're creating the link in.
85 * @kobj: object whose directory we're creating the link in.
98 * @kobj: object whose directory we're creating the link in.
|
| /linux-6.14.4/Documentation/driver-api/phy/ |
| D | phy.rst | 21 The intention of creating this framework is to bring the PHY drivers spread
74 Creating the PHY
94 can use phy_set_drvdata() after creating the PHY and use phy_get_drvdata() in
190 This subsystem is pm runtime enabled. So while creating the PHY,
|
| /linux-6.14.4/Documentation/isdn/ |
| D | credits.rst | 23 For creating and maintaining the FAQ.
26 For creating the FAQ, and the leafsite HOWTO.
|
| /linux-6.14.4/Documentation/networking/ |
| D | mptcp.rst | 91 Creating MPTCP sockets
94 On Linux, MPTCP can be used by selecting MPTCP instead of TCP when creating the
151 kernel is in charge of creating subflow sockets: they are TCP sockets where the
|
| /linux-6.14.4/tools/testing/selftests/bpf/prog_tests/ |
| D | test_bpffs.c | 80 if (!ASSERT_OK(err, "creating " TDIR "/fs1/a")) in fn()
83 if (!ASSERT_OK(err, "creating " TDIR "/fs1/a/1")) in fn()
86 if (!ASSERT_OK(err, "creating " TDIR "/fs1/b")) in fn()
|
| /linux-6.14.4/tools/testing/selftests/rcutorture/bin/ |
| D | mkinitrd.sh | 24 echo "Creating a statically linked C-language initrd"
93 echo "Done creating a statically linked C-language initrd"
|
| /linux-6.14.4/Documentation/driver-api/media/ |
| D | v4l2-intro.rst | 18 creating V4L device nodes and video_buf for handling the video buffers
46 3) Creating V4L2 device nodes (/dev/videoX, /dev/vbiX and /dev/radioX)
|
| /linux-6.14.4/Documentation/admin-guide/acpi/ |
| D | ssdt-overlays.rst | 12 Although this can be accomplished by creating a kernel platform driver or
118 Creating a new file in /sys/firmware/efi/efivars will automatically create a new
176 New tables can be loading by creating new directories in /sys/kernel/config/acpi/table
|
| /linux-6.14.4/Documentation/PCI/endpoint/ |
| D | pci-vntb-howto.rst | 45 Creating pci-epf-vntb Device
137 "Creating pci-epf-ntb Device" section above::
150 "Creating pci-epf-ntb Device" section above::
|
| /linux-6.14.4/Documentation/filesystems/ |
| D | hfs.rst | 26 used for creating new files. Default values: '????'.
74 Creating HFS filesystems
|
| /linux-6.14.4/tools/testing/selftests/sync/ |
| D | sync_stress_merge.c | 53 ASSERT(valid, "Failure creating fence\n"); in test_merge_stress_random_merge()
82 ASSERT(valid, "Failure creating fence i\n"); in test_merge_stress_random_merge()
|
| /linux-6.14.4/drivers/rpmsg/ |
| D | rpmsg_internal.h | 33 * advertise new channels implicitly by creating the endpoints.
92 * @rpdev: prepared rpdev to be used for creating endpoints
|