Searched full:strictly (Results 1 – 25 of 488) sorted by relevance
12345678910>>...20
| /linux-6.14.4/drivers/gpu/drm/i915/gt/ |
| D | intel_ring.h | 71 if (pos & -ring->size) /* must be strictly within the ring */ in intel_ring_offset_valid()
118 /* Whilst writes to the tail are strictly order, there is no in intel_ring_set_tail()
|
| /linux-6.14.4/Documentation/ |
| D | atomic_t.txt | 67 Therefore, an explicitly unsigned variant of the atomic ops is strictly
225 is a 'typical' RELEASE pattern, the barrier is strictly stronger than
234 strictly stronger than ACQUIRE. As illustrated:
|
| /linux-6.14.4/arch/riscv/include/asm/vendor_extensions/ |
| D | andes.h | 12 * Extension keys should be strictly less than max.
|
| D | thead.h | 10 * Extension keys must be strictly less than RISCV_ISA_VENDOR_EXT_MAX.
|
| /linux-6.14.4/include/dt-bindings/reset/ |
| D | imx7-reset.h | 40 * IMX7_RESET_PCIE_CTRL_APPS_EN is not strictly a reset line, but it
|
| /linux-6.14.4/include/linux/ |
| D | of_gpio.h | 29 /* Drivers may not strictly depend on the GPIO support, so let them link. */
|
| /linux-6.14.4/drivers/ssb/ |
| D | Makefile | 24 # Not strictly a part of SSB, but kept here for convenience
|
| /linux-6.14.4/drivers/net/ethernet/intel/i40e/ |
| D | i40e_xsk.h | 10 * macro. Why 4? It is strictly empirical. It seems to be a good
|
| /linux-6.14.4/drivers/firmware/efi/libstub/ |
| D | riscv-stub.c | 19 * strictly not part of the in-memory presentation of the image, only in stext_offset()
|
| D | arm64-stub.c | 53 * strictly not part of the in-memory presentation of the image, only in primary_entry_offset()
|
| /linux-6.14.4/Documentation/devicetree/bindings/misc/ |
| D | ifm-csi.txt | 9 GPIOs (strictly in this order).
|
| /linux-6.14.4/net/ipv6/ |
| D | exthdrs_core.c | 30 * Note that strictly speaking this conflicts with RFC 2460 4.0:
33 * be processed strictly in the order they appear in the packet; a
|
| /linux-6.14.4/include/net/ |
| D | inet_dscp.h | 30 * Using dscp_t allows to strictly separate DSCP and ECN bits, thus avoiding
|
| /linux-6.14.4/Documentation/core-api/ |
| D | tracepoint.rst | 13 a callback mechanism. The 'probes' are strictly typed functions that are
|
| D | circular-buffers.rst | 56 Typically, items will all be of the same unit size, but this isn't strictly
223 reloading its cached value. This isn't strictly needed if you can
|
| /linux-6.14.4/Documentation/driver-api/firmware/ |
| D | firmware-usage-guidelines.rst | 13 then of course these rules will not apply strictly.)
|
| /linux-6.14.4/tools/lib/ |
| D | argv_split.c | 57 * @str. This is performed by strictly splitting on white-space; no
|
| /linux-6.14.4/Documentation/maintainer/ |
| D | modifying-patches.rst | 8 exactly the same in your tree and the submitters'. If you stick strictly to
|
| /linux-6.14.4/arch/riscv/include/asm/ |
| D | vendor_extensions.h | 15 * The extension keys of each vendor must be strictly less than this value.
|
| /linux-6.14.4/drivers/hid/usbhid/ |
| D | Kconfig | 39 specification standpoint) that aren't strictly user interface
|
| /linux-6.14.4/tools/testing/selftests/powerpc/copyloops/ |
| D | Makefile | 37 # Strictly speaking, we only need the memcpy_64 test cases for big-endian
|
| /linux-6.14.4/lib/ |
| D | argv_split.c | 50 * @str. This is performed by strictly splitting on white-space; no
|
| /linux-6.14.4/arch/arm/kernel/ |
| D | perf_callchain.c | 53 * Frame pointers should strictly progress back up the stack in user_backtrace()
|
| /linux-6.14.4/Documentation/misc-devices/ |
| D | tps6594-pfsm.rst | 12 Strictly speaking, PFSM (Pre-configurable Finite State Machine) is not
|
| /linux-6.14.4/arch/x86/include/asm/ |
| D | bug.h | 86 * This instrumentation_begin() is strictly speaking incorrect; but it
|
12345678910>>...20