| /OK3568_Linux_fs/yocto/poky/meta/recipes-extended/mdadm/files/ |
| H A D | 0001-mdadm-Fix-optional-write-behind-parameter.patch | 4 Subject: [PATCH] mdadm: Fix optional --write-behind parameter
6 The commit noted below changed the behaviour of --write-behind to
9 mdadm: Invalid value for maximum outstanding write-behind writes: (null).
40 …pr_err("Invalid value for maximum outstanding write-behind writes: %s.\n\tMust be between 0 and 16…
|
| /OK3568_Linux_fs/kernel/fs/ubifs/ |
| H A 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()
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | sysfs-ata | 21 connected, the number of links behind it.
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
121 "none" if no device was found behind the link.
|
| /OK3568_Linux_fs/kernel/drivers/md/ |
| H A D | md-bitmap.h | 255 unsigned long sectors, int behind);
257 unsigned long sectors, int success, int behind);
|
| /OK3568_Linux_fs/buildroot/package/libtool/ |
| H A D | Config.in | 5 libraries on different platforms behind a consistent, portable
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/usb/ |
| H A D | ulpi.txt | 4 Phys that are behind a ULPI connection can be described with the following
|
| /OK3568_Linux_fs/buildroot/package/parprouted/ |
| H A D | Config.in | 10 Ethernet networks behind wireless nodes without using WDS or
|
| /OK3568_Linux_fs/kernel/Documentation/firmware-guide/acpi/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/mei/ |
| H A D | nfc.rst | 6 Some Intel 8 and 9 Serieses chipsets supports NFC devices connected behind
|
| /OK3568_Linux_fs/kernel/drivers/clk/versatile/ |
| H A D | Kconfig | 28 Express platforms hidden behind its configuration infrastructure,
|
| /OK3568_Linux_fs/buildroot/package/siproxd/ |
| H A D | Config.in | 16 as those from Cisco, Grandstream or Snom) to work behind an IP
|
| /OK3568_Linux_fs/buildroot/package/igd2-for-linux/ |
| H A D | Config.in | 16 MSN Messenger, Azureus or Miranda to work properly from behind
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-extended/liblogging/ |
| H A D | liblogging_1.0.6.bb | 7 sophisticated "behind the scenes" with better support for multiple threads \
|
| /OK3568_Linux_fs/buildroot/package/ripgrep/ |
| H A D | 0001-puts-jemalloc-allocator-behind-a-cargo-feature-flag.patch | 4 Subject: [PATCH] puts jemalloc allocator behind a cargo feature flag
8 Moves jemalloc behind a feature for musl builds, where it is not
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/pci/ |
| H A 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
|
| /OK3568_Linux_fs/buildroot/package/softether/ |
| H A D | Config.in | 22 routing domain, even behind a NAT or without a static IPv4
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/i2c/ |
| H A D | i2c-gate.txt | 23 Kasei ak8975 compass behind a gate.
|
| H A D | i2c-mux-ltc4306.txt | 19 multiplexers on the bus and the devices behind them use same I2C addresses.
|
| /OK3568_Linux_fs/kernel/Documentation/x86/ |
| H A D | booting-dt.rst | 21 otherwise like interrupt routing or a list of devices behind an I2C bus.
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/python/python3/ |
| H A D | deterministic_imports.patch | 4 Secondly, empty directories left behind by previous modules might be looked at. This
|
| /OK3568_Linux_fs/buildroot/package/iprutils/ |
| H A D | 0001-configure.ac-add-AC_USE_SYSTEM_EXTENSIONS.patch | 7 they were guarded behind different sets of feature-test macros (see
|
| /OK3568_Linux_fs/kernel/Documentation/filesystems/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/crypto/ |
| H A D | hisilicon,hip07-sec.txt | 22 - iommus: The SEC units are behind smmu-v3 iommus.
|
| /OK3568_Linux_fs/kernel/Documentation/i2c/ |
| H A D | i2c-topology.rst | 14 from the I2C bus, at least most of the time, and sits behind a gate
104 address 0x42 behind mux-one may be interleaved with a similar
105 operation targeting device address 0x42 behind mux-two. The
118 behind the mux, when an unrelated I2C transfer is in flight during
|
| /OK3568_Linux_fs/kernel/drivers/usb/isp1760/ |
| H A D | Kconfig | 13 where the chip itself is behind a PLB to simulate such
|