| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-ata | 21 connected, the number of links behind it.
40 Behind each port, there is a ata_link. If there is a SATA PM in the topology, 15
43 If a link is behind a port, the directory name is linkX, where X is ata_port_id
44 of the port. If a link is behind a PM, its name is linkX.Y where X is
67 Behind each link, up to two ata devices are created.
121 "none" if no device was found behind the link.
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-ata | 21 connected, the number of links behind it.
40 Behind each port, there is a ata_link. If there is a SATA PM in the topology, 15
43 If a link is behind a port, the directory name is linkX, where X is ata_port_id
44 of the port. If a link is behind a PM, its name is linkX.Y where X is
67 Behind each link, up to two ata devices are created.
121 "none" if no device was found behind the link.
|
| /kernel/linux/linux-5.10/drivers/md/ |
| D | raid1.h | 155 atomic_t behind_remaining; /* number of write-behind ios remaining
174 * When R1BIO_BehindIO is set, we store pages for write behind
197 /* For write-behind requests, we call bi_end_io when
198 * the last non-write-behind device completes, providing
200 * any write-behind write succeeds, otherwise we call
|
| /kernel/linux/linux-6.6/drivers/md/ |
| D | raid1.h | 154 atomic_t behind_remaining; /* number of write-behind ios remaining
173 * When R1BIO_BehindIO is set, we store pages for write behind
195 /* For write-behind requests, we call bi_end_io when
196 * the last non-write-behind device completes, providing
198 * any write-behind write succeeds, otherwise we call
|
| /kernel/linux/linux-6.6/tools/testing/selftests/drivers/net/mlxsw/ |
| D | tc_restrictions.sh | 215 check_fail $? "Incorrect success to add matchall rule behind a flower rule"
224 check_err $? "Failed to add flower rule behind a matchall rule"
254 # On egress, all matchall-mirror rules have to be behind the flower rules
269 check_fail $? "Incorrect success to add matchall rule behind a flower rule"
278 check_err $? "Failed to add flower rule behind a matchall rule"
|
| /kernel/linux/linux-5.10/tools/testing/selftests/drivers/net/mlxsw/ |
| D | tc_restrictions.sh | 211 check_fail $? "Incorrect success to add matchall rule behind a flower rule"
220 check_err $? "Failed to add flower rule behind a matchall rule"
250 # On egress, all matchall-mirror rules have to be behind the flower rules
265 check_fail $? "Incorrect success to add matchall rule behind a flower rule"
274 check_err $? "Failed to add flower rule behind a matchall rule"
|
| /kernel/linux/linux-6.6/arch/mips/vdso/ |
| D | vgettimeofday.c | 23 * This is behind the ifdef so that we don't provide the symbol when there's no
59 * This is behind the ifdef so that we don't provide the symbol when there's no
|
| /kernel/linux/linux-5.10/arch/mips/vdso/ |
| D | vgettimeofday.c | 23 * This is behind the ifdef so that we don't provide the symbol when there's no
59 * This is behind the ifdef so that we don't provide the symbol when there's no
|
| /kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/ |
| D | enumeration.rst | 9 devices behind serial bus controllers.
21 - Devices behind real busses where there is a connector resource
29 The ACPI implementation enumerates devices behind busses (platform, SPI and
149 Slave devices behind SPI bus have SpiSerialBus resource attached to them.
232 The slaves behind I2C bus controller only need to add the ACPI IDs like
234 any slave devices behind the controller device once the adapter is
|
| /kernel/linux/linux-6.6/arch/sparc/kernel/ |
| D | trampoline_32.S | 50 /* Our %wim is one behind CWP */
104 /* Our %wim is one behind CWP */
163 /* Our %wim is one behind CWP */
|
| /kernel/linux/linux-5.10/arch/sparc/kernel/ |
| D | trampoline_32.S | 50 /* Our %wim is one behind CWP */
104 /* Our %wim is one behind CWP */
163 /* Our %wim is one behind CWP */
|
| /kernel/linux/linux-6.6/Documentation/driver-api/pci/ |
| D | p2pdma.rst | 17 only supports doing P2P when the endpoints involved are all behind the
61 memory behind it, its driver could add support as a P2P provider and
123 effects behind it. Thus, the order of loads and stores should not be important
|
| /kernel/linux/linux-5.10/fs/ubifs/ |
| D | master.c | 27 int behind; in ubifs_compare_master_node() local
43 behind = hmac_offs + UBIFS_MAX_HMAC_LEN; in ubifs_compare_master_node()
45 if (UBIFS_MST_NODE_SZ > behind) in ubifs_compare_master_node()
46 return memcmp(m1 + behind, m2 + behind, UBIFS_MST_NODE_SZ - behind); in ubifs_compare_master_node()
|
| /kernel/linux/linux-6.6/fs/ubifs/ |
| D | master.c | 27 int behind; in ubifs_compare_master_node() local
43 behind = hmac_offs + UBIFS_MAX_HMAC_LEN; in ubifs_compare_master_node()
45 if (UBIFS_MST_NODE_SZ > behind) in ubifs_compare_master_node()
46 return memcmp(m1 + behind, m2 + behind, UBIFS_MST_NODE_SZ - behind); in ubifs_compare_master_node()
|
| /kernel/linux/linux-6.6/drivers/fsi/ |
| D | Kconfig | 60 This option enables a FSI master that is present behind an OPB bridge
70 behind an IBM I2C Responder (I2CR) chip. The I2CR is an I2C device
|
| /kernel/linux/linux-5.10/Documentation/driver-api/pci/ |
| D | p2pdma.rst | 17 only supports doing P2P when the endpoints involved are all behind the
61 memory behind it, its driver could add support as a P2P provider and
133 effects behind it. Thus, the order of loads and stores should not be important
|
| /kernel/linux/linux-6.6/drivers/firmware/efi/libstub/ |
| D | pci.c | 59 * Disregard devices living on bus 0 - these are not behind a in efi_pci_disable_bridge_busmaster()
70 * controllers that are behind a PCIe root port do not use in efi_pci_disable_bridge_busmaster()
|
| /kernel/linux/linux-5.10/drivers/firmware/efi/libstub/ |
| D | pci.c | 59 * Disregard devices living on bus 0 - these are not behind a in efi_pci_disable_bridge_busmaster()
70 * controllers that are behind a PCIe root port do not use in efi_pci_disable_bridge_busmaster()
|
| /kernel/linux/linux-5.10/tools/perf/tests/ |
| D | maps.c | 94 /* kcore2 map hides behind bpf_prog_2 */ in test__maps__merge_in()
98 /* kcore3 map hides behind bpf_prog_3, kcore1 and adds new map */ in test__maps__merge_in()
|
| /kernel/linux/linux-6.6/drivers/soundwire/ |
| D | intel_ace2x_debugfs.c | 94 /* Userspace changed the hardware state behind the kernel's back */ in intel_set_m_datamode()
112 /* Userspace changed the hardware state behind the kernel's back */ in intel_set_s_datamode()
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | inotify.rst | 18 What is the design decision behind not tying the watch to the open fd of
29 What is the design decision behind using an-fd-per-instance as opposed to
|
| /kernel/linux/linux-6.6/tools/perf/tests/ |
| D | maps.c | 117 /* kcore2 map hides behind bpf_prog_2 */ in test__maps__merge_in()
121 /* kcore3 map hides behind bpf_prog_3, kcore1 and adds new map */ in test__maps__merge_in()
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | inotify.rst | 18 What is the design decision behind not tying the watch to the open fd of
29 What is the design decision behind using an-fd-per-instance as opposed to
|
| /kernel/linux/linux-6.6/Documentation/firmware-guide/acpi/ |
| D | enumeration.rst | 9 devices behind serial bus controllers.
21 - Devices behind real busses where there is a connector resource
30 The ACPI implementation enumerates devices behind busses (platform, SPI,
186 Slave devices behind SPI bus have SpiSerialBus resource attached to them.
261 The slaves behind I2C bus controller only need to add the ACPI IDs like
263 any slave devices behind the controller device once the adapter is
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/usb/ |
| D | ulpi.txt | 4 Phys that are behind a ULPI connection can be described with the following
|