Home
last modified time | relevance | path

Searched full:relied (Results 1 – 25 of 73) sorted by relevance

123

/openbmc/openbmc/meta-phosphor/recipes-support/boost/
H A Dboost_%.bbappend7 #be relied directly, but are required dependencies of context and coroutine.
/openbmc/linux/Documentation/driver-api/firmware/
H A Dlookup-order.rst19 is issued or the custom firmware loading is relied upon for firmware
/openbmc/linux/include/linux/sched/
H A Dstat.h13 * so they can only be relied on in narrow circumstances. )
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Object/
H A DEnable.interface.yaml6 the object properties) can't be relied upon, until the object is "enabled"
/openbmc/openbmc/poky/documentation/migration-guides/
H A Dmigration-1.4.rst59 :term:`FILESOVERRIDES` as well. However, if you relied upon an additional
125 :term:`SRC_URI`. If you have a recipe that relied upon
/openbmc/linux/Documentation/ABI/stable/
H A Dsysfs-firmware-opal-dump17 directory should not be relied upon to
/openbmc/bmcweb/
H A DHEADERS.md38 of requests/responses, relied on APIs that should've been internal, and other
/openbmc/linux/fs/reiserfs/
H A Dlock.c10 * - the performances relied on the release-while-schedule() property
/openbmc/linux/drivers/mtd/devices/
H A Dms02-nv.h44 * stored in the SRAM cannot be relied upon. But from the hardware
/openbmc/linux/tools/testing/selftests/bpf/progs/
H A Drbtree.c217 * Previously we relied on the verifier type system + rbtree_remove in rbtree_api_release_aliasing()
/openbmc/openbmc/poky/meta/recipes-core/ovmf/ovmf/
H A D0003-debug-prefix-map.patch14 Previously we relied on the stripped output being the same which isn't always
/openbmc/linux/Documentation/scheduler/
H A Dsched-rt-group.rst47 relied upon. Which leaves us with just the single fixed portion.
/openbmc/linux/Documentation/block/
H A Dbiovecs.rst106 * bi_vcnt can't be trusted or relied upon by driver code - i.e. anything that
/openbmc/linux/drivers/base/firmware_loader/
H A DKconfig117 can no longer be relied upon as a fallback mechanism. Linux no longer
/openbmc/linux/Documentation/hid/
H A Dhidraw.rst29 Hidraw uses a dynamic major number, meaning that udev should be relied on to
/openbmc/linux/block/
H A Dbounce.c161 * - Lastly, bi_vcnt should not be looked at or relied upon by code in bounce_clone_bio()
/openbmc/linux/arch/parisc/include/asm/
H A Dassembly.h523 /* First step to create a "relied upon translation"
550 rsm PSW_SM_I, %r0 /* barrier for "Relied upon Translation */
/openbmc/linux/rust/kernel/
H A Dstd_vendor.rs47 /// The exact output printed by this macro should not be relied upon
/openbmc/linux/Documentation/driver-api/surface_aggregator/clients/
H A Dcdev.rst14 therefore should not be used or relied upon in any other way. Note that this
/openbmc/linux/include/linux/
H A Dvmalloc.h187 * relied upon the compiler to optimize calls out if ARCH_PAGE_TABLE_SYNC_MASK
/openbmc/linux/include/linux/surface_aggregator/
H A Dserial_hub.h454 * This callback must be relied upon to ensure that the packet has
575 * This callback must be relied upon to ensure that the request has
/openbmc/linux/net/rds/
H A Dthreads.c107 * This random exponential backoff is relied on to eventually resolve racing
/openbmc/linux/Documentation/filesystems/
H A Dporting.rst84 Most likely there is no need to change anything, but if you relied on
687 in-tree instances relied upon that.
992 umount(2) relied on the file_system_type as the holder. This was severly
/openbmc/linux/Documentation/usb/
H A Dmass-storage.rst78 the default values. Also, if one relied on old default, explicit
/openbmc/linux/Documentation/powerpc/
H A Dsyscall64-abi.rst108 behavior should not be relied upon.

123