Searched full:strictly (Results 1 – 25 of 860) sorted by relevance
12345678910>>...35
| /kernel/linux/linux-5.10/arch/x86/oprofile/ |
| D | backtrace.c | 38 /* frame pointers should strictly progress back up the stack in dump_user_backtrace_32()
82 /* frame pointers should strictly progress back up the stack in dump_user_backtrace()
|
| /kernel/linux/linux-5.10/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:
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/i915/gt/ |
| D | intel_ring.h | 72 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()
|
| /kernel/linux/linux-6.6/arch/arm64/kernel/ |
| D | perf_callchain.c | 46 * Frame pointers should strictly progress back up the stack in user_backtrace()
91 * Frame pointers should strictly progress back up the stack in compat_user_backtrace()
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/i915/gt/ |
| D | intel_ring.h | 72 if (pos & -ring->size) /* must be strictly within the ring */ in intel_ring_offset_valid()
119 /* Whilst writes to the tail are strictly order, there is no in intel_ring_set_tail()
|
| /kernel/linux/linux-5.10/drivers/power/supply/ |
| D | ab8500_bmdata.c | 12 * Note that the res_to_temp table must be strictly sorted by falling resistance
133 * Note that the res_to_temp table must be strictly sorted by falling
155 * Note that the batres_vs_temp table must be strictly sorted by falling
169 * Note that the batres_vs_temp table must be strictly sorted by falling
|
| /kernel/linux/linux-5.10/arch/arm64/kernel/ |
| D | perf_callchain.c | 46 * Frame pointers should strictly progress back up the stack in user_backtrace()
91 * Frame pointers should strictly progress back up the stack in compat_user_backtrace()
|
| /kernel/linux/linux-6.6/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:
|
| /kernel/linux/linux-5.10/include/dt-bindings/reset/ |
| D | imx7-reset.h | 40 * IMX7_RESET_PCIE_CTRL_APPS_EN is not strictly a reset line, but it
|
| /kernel/linux/linux-6.6/include/dt-bindings/reset/ |
| D | imx7-reset.h | 40 * IMX7_RESET_PCIE_CTRL_APPS_EN is not strictly a reset line, but it
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | of_gpio.h | 29 /* Drivers may not strictly depend on the GPIO support, so let them link. */
|
| /kernel/linux/linux-5.10/drivers/ssb/ |
| D | Makefile | 24 # Not strictly a part of SSB, but kept here for convenience
|
| /kernel/linux/linux-6.6/drivers/ssb/ |
| D | Makefile | 24 # Not strictly a part of SSB, but kept here for convenience
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/intel/i40e/ |
| D | i40e_xsk.h | 10 * macro. Why 4? It is strictly empirical. It seems to be a good
|
| /kernel/linux/linux-5.10/drivers/soundwire/ |
| D | intel.h | 27 void __iomem *mmio_base; /* not strictly needed, useful for debug */
|
| /kernel/linux/linux-6.6/drivers/firmware/efi/libstub/ |
| D | riscv-stub.c | 19 * strictly not part of the in-memory presentation of the image, only in stext_offset()
|
| /kernel/linux/linux-5.10/arch/x86/include/asm/ |
| D | vmware.h | 19 * In short, new driver code should strictly use the new definition of
|
| /kernel/linux/linux-6.6/arch/x86/include/asm/ |
| D | vmware.h | 19 * In short, new driver code should strictly use the new definition of
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/misc/ |
| D | ifm-csi.txt | 9 GPIOs (strictly in this order).
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/misc/ |
| D | ifm-csi.txt | 9 GPIOs (strictly in this order).
|
| /kernel/linux/linux-6.6/Documentation/core-api/ |
| D | tracepoint.rst | 13 a callback mechanism. The 'probes' are strictly typed functions that are
|
| /kernel/linux/linux-6.6/include/net/ |
| D | inet_dscp.h | 30 * Using dscp_t allows to strictly separate DSCP and ECN bits, thus avoiding
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | tracepoint.rst | 13 a callback mechanism. The 'probes' are strictly typed functions that are
|
| /kernel/linux/linux-6.6/arch/ia64/scripts/ |
| D | toolchain-flags | 25 the kernel will be bigger than strictly necessary).
|
| /kernel/linux/linux-5.10/arch/ia64/scripts/ |
| D | toolchain-flags | 25 the kernel will be bigger than strictly necessary).
|
12345678910>>...35