Home
last modified time | relevance | path

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

12345678910>>...24

/openbmc/openbmc/poky/bitbake/lib/prserv/
H A D__init__.py62 Returns True if rev1 is strictly smaller than rev2"""
67 Returns True if rev1 is strictly greater than rev2"""
/openbmc/linux/arch/arm64/kernel/
H A Dperf_callchain.c46 * 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()
/openbmc/qemu/util/
H A Drange.c44 /* Skip all list elements strictly less than data */ in range_list_insert()
49 /* Rest of the list (if any) is strictly greater than @data */ in range_list_insert()
/openbmc/linux/drivers/gpu/drm/i915/gt/
H A Dintel_ring.h72 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()
/openbmc/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:
/openbmc/openbmc/poky/meta/recipes-graphics/xorg-lib/
H A Dxcb-util.inc6 of the libraries also provide client-side code which is not strictly \
/openbmc/qemu/accel/tcg/
H A Dtb-jmp-cache.h22 * non-NULL value of 'tb'. Strictly speaking pc is only needed for
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/tclap/
H A Dtclap_1.4.0.bb7 objects, such as IntArg, FloatArg, and StringArg. While the library is not strictly \
/openbmc/phosphor-pid-control/
H A Dmeson.options12 description: 'Set the fans strictly at the failsafe PWM when in failsafe mode',
/openbmc/linux/include/linux/
H A Dof_gpio.h29 /* Drivers may not strictly depend on the GPIO support, so let them link. */
/openbmc/linux/include/dt-bindings/reset/
H A Dimx7-reset.h40 * IMX7_RESET_PCIE_CTRL_APPS_EN is not strictly a reset line, but it
/openbmc/u-boot/arch/x86/include/asm/arch-quark/
H A Dquark.h238 * enumeration process are strictly forbidden, as any access to PCIe root
251 * enumeration process are strictly forbidden, as any access to PCIe root
/openbmc/linux/drivers/ssb/
H A DMakefile24 # Not strictly a part of SSB, but kept here for convenience
/openbmc/linux/drivers/net/ethernet/intel/i40e/
H A Di40e_xsk.h10 * macro. Why 4? It is strictly empirical. It seems to be a good
/openbmc/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.c60 * strictly not part of the in-memory presentation of the image, only in primary_entry_offset()
/openbmc/linux/Documentation/devicetree/bindings/misc/
H A Difm-csi.txt9 GPIOs (strictly in this order).
/openbmc/linux/arch/x86/include/asm/
H A Dvmware.h19 * In short, new driver code should strictly use the new definition of
/openbmc/linux/include/net/
H A Dinet_dscp.h30 * Using dscp_t allows to strictly separate DSCP and ECN bits, thus avoiding
/openbmc/linux/Documentation/core-api/
H A Dtracepoint.rst13 a callback mechanism. The 'probes' are strictly typed functions that are
/openbmc/linux/arch/ia64/scripts/
H A Dtoolchain-flags25 the kernel will be bigger than strictly necessary).
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/packagegroups/
H A Dpackagegroup-basic.bb37 # 3) Nice to have: packages that are nice to have, but aren't strictly needed
/openbmc/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
/openbmc/linux/Documentation/driver-api/firmware/
H A Dfirmware-usage-guidelines.rst13 then of course these rules will not apply strictly.)
/openbmc/openbmc/meta-security/docs/
H A Ddm-verity-systemd-hash-x86-64.txt40 While not strictly coupled to any functionality at this point in time, it

12345678910>>...24