Home
last modified time | relevance | path

Searched full:strictly (Results 1 – 25 of 447) sorted by relevance

12345678910>>...18

/linux/tools/testing/selftests/sched_ext/
H A Dallowed_cpus.bpf.c4 * selecting idle CPUs strictly within a subset of allowed CPUs.
42 * Select an idle CPU strictly within the allowed domain. in BPF_STRUCT_OPS()
/linux/drivers/gpu/drm/i915/gt/
H A Dintel_ring.h71 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/Documentation/filesystems/
H A Dpropagate_umount.txt13 to S all subtrees mounted strictly inside of X (i.e. not overmounting
110 subtree mounted strictly inside m and containing mounts that do not
137 mountpoint strictly inside x.
139 belonging to S is mounted strictly inside x.
159 mountpoint of x_1 is strictly inside x. If mount r belongs to S, it must
363 in S - {x} and a subtree mounted strictly inside m, such that m contains
/linux/arch/riscv/include/asm/vendor_extensions/
H A Dandes.h12 * Extension keys should be strictly less than max.
H A Dthead.h10 * Extension keys must be strictly less than RISCV_ISA_VENDOR_EXT_MAX.
/linux/Documentation/
H A Datomic_t.txt67 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/Documentation/userspace-api/fwctl/
H A Dfwctl.rst72 fwctl drivers are strictly restricted to being a way to operate the device FW.
106 3. Write access to function & child debug information strictly compatible with
227 RPC interface does not have to meet a strictly stable ABI, but it does need to
/linux/include/dt-bindings/reset/
H A Dimx7-reset.h40 * IMX7_RESET_PCIE_CTRL_APPS_EN is not strictly a reset line, but it
/linux/include/linux/
H A Dof_gpio.h29 /* Drivers may not strictly depend on the GPIO support, so let them link. */
/linux/drivers/ssb/
H A DMakefile24 # Not strictly a part of SSB, but kept here for convenience
/linux/drivers/net/ethernet/intel/i40e/
H A Di40e_xsk.h10 * macro. Why 4? It is strictly empirical. It seems to be a good
/linux/drivers/firmware/efi/libstub/
H A Driscv-stub.c19 * strictly not part of the in-memory presentation of the image, only in stext_offset()
H A Darm64-stub.c53 * strictly not part of the in-memory presentation of the image, only in primary_entry_offset()
/linux/Documentation/devicetree/bindings/misc/
H A Difm-csi.txt9 GPIOs (strictly in this order).
/linux/Documentation/core-api/
H A Dtracepoint.rst13 a callback mechanism. The 'probes' are strictly typed functions that are
H A Dcircular-buffers.rst56 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/include/net/
H A Dinet_dscp.h30 * Using dscp_t allows to strictly separate DSCP and ECN bits, thus avoiding
/linux/net/ipv6/
H A Dexthdrs_core.c30 * 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/tools/lib/
H A Dargv_split.c57 * @str. This is performed by strictly splitting on white-space; no
/linux/arch/riscv/include/asm/
H A Dvendor_extensions.h15 * The extension keys of each vendor must be strictly less than this value.
/linux/Documentation/maintainer/
H A Dmodifying-patches.rst8 exactly the same in your tree and the submitters'. If you stick strictly to
/linux/Documentation/driver-api/firmware/
H A Dfirmware-usage-guidelines.rst13 then of course these rules will not apply strictly.)
/linux/drivers/hid/usbhid/
H A DKconfig39 specification standpoint) that aren't strictly user interface
/linux/arch/arm/kernel/
H A Dperf_callchain.c53 * Frame pointers should strictly progress back up the stack in user_backtrace()
/linux/lib/
H A Dargv_split.c50 * @str. This is performed by strictly splitting on white-space; no

12345678910>>...18