Home
last modified time | relevance | path

Searched full:behind (Results 1 – 25 of 1085) sorted by relevance

12345678910>>...44

/kernel/linux/linux-4.19/Documentation/ABI/testing/
Dsysfs-ata21 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.
120 "none" if no device was found behind the link.
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-ata21 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.
120 "none" if no device was found behind the link.
/kernel/linux/linux-5.10/drivers/md/
Draid1.h155 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-4.19/drivers/md/
Draid1.h155 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-5.10/tools/testing/selftests/drivers/net/mlxsw/
Dtc_restrictions.sh211 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-5.10/arch/mips/vdso/
Dvgettimeofday.c23 * 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-4.19/Documentation/acpi/
Denumeration.txt5 devices behind serial bus controllers.
17 o Devices behind real busses where there is a connector resource
25 The ACPI implementation enumerates devices behind busses (platform, SPI and
142 Slave devices behind SPI bus have SpiSerialBus resource attached to them.
224 The slaves behind I2C bus controller only need to add the ACPI IDs like
226 any slave devices behind the controller device once the adapter is
/kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/
Denumeration.rst9 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-4.19/arch/sparc/kernel/
Dtrampoline_32.S50 /* 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/
Dtrampoline_32.S50 /* 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/fs/ubifs/
Dmaster.c27 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-5.10/Documentation/driver-api/pci/
Dp2pdma.rst17 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-4.19/arch/s390/boot/compressed/
Dmisc.c94 * Move the initrd right behind the end of the decompressed in decompress_kernel()
96 * bss clearing since kernel_end will always be located behind the in decompress_kernel()
/kernel/linux/linux-5.10/drivers/firmware/efi/libstub/
Dpci.c59 * 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/
Dmaps.c94 /* 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-4.19/Documentation/filesystems/
Dinotify.txt12 Q: What is the design decision behind not tying the watch to the open fd of
21 Q: What is the design decision behind using an-fd-per-instance as opposed to
/kernel/linux/linux-5.10/Documentation/filesystems/
Dinotify.rst18 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-4.19/sound/drivers/
Dpcm-indirect2.h66 * exception that sw_data is "behind" by the number if bytes ALSA wrote
76 * to be as much bytes which were played. So sw_io will stay behind
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/usb/
Dulpi.txt4 Phys that are behind a ULPI connection can be described with the following
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/usb/
Dulpi.txt4 Phys that are behind a ULPI connection can be described with the following
/kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/toshiba/
Dspider_net.rst47 flowing RX traffic, every descr behind it should be marked "full",
57 all of those behind it should be "not-in-use". When RX traffic is not
69 be "not-in-use", and everything behind it should be "empty". If no
/kernel/linux/linux-4.19/Documentation/networking/
Dspider_net.txt45 flowing RX traffic, every descr behind it should be marked "full",
55 all of those behind it should be "not-in-use". When RX traffic is not
67 be "not-in-use", and everything behind it should be "empty". If no
/kernel/linux/linux-4.19/drivers/char/agp/
Disoch.c61 * lying behind it...)
316 * lying behind it.
341 * (multiple AGP v3 devices are allowed behind a single bridge). in agp_3_5_enable()
389 * Take an initial pass through the devices lying behind our host in agp_3_5_enable()
/kernel/linux/linux-5.10/drivers/char/agp/
Disoch.c61 * lying behind it...)
311 * lying behind it.
334 * (multiple AGP v3 devices are allowed behind a single bridge). in agp_3_5_enable()
382 * Take an initial pass through the devices lying behind our host in agp_3_5_enable()
/kernel/linux/linux-4.19/drivers/clk/versatile/
DKconfig31 Express platforms hidden behind its configuration infrastructure,

12345678910>>...44