Home
last modified time | relevance | path

Searched full:entirely (Results 1 – 25 of 806) sorted by relevance

12345678910>>...33

/openbmc/u-boot/lib/libavb/
H A Davb_vbmeta_image.c94 /* Ensure hash and signature are entirely in the Authentication data block. */ in avb_vbmeta_image_verify()
98 avb_error("Hash is not entirely in its block.\n"); in avb_vbmeta_image_verify()
104 avb_error("Signature is not entirely in its block.\n"); in avb_vbmeta_image_verify()
108 /* Ensure public key is entirely in the Auxiliary data block. */ in avb_vbmeta_image_verify()
112 avb_error("Public key is not entirely in its block.\n"); in avb_vbmeta_image_verify()
116 /* Ensure public key metadata (if set) is entirely in the Auxiliary in avb_vbmeta_image_verify()
124 avb_error("Public key metadata is not entirely in its block.\n"); in avb_vbmeta_image_verify()
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/
H A Dpinctrl.yaml18 entirely by the binding for the individual pin controller device. There
25 nodes, is again defined entirely by the binding for the individual pin
/openbmc/qemu/linux-user/
H A Dflat.h46 #define FLAT_FLAG_RAM 0x0001 /* load program entirely into RAM */
67 # define OLD_FLAT_FLAG_RAM 0x1 /* load program entirely into RAM */
/openbmc/qemu/docs/devel/
H A Dcontrol-flow-integrity.rst19 This type of CFI is entirely compiler-based and relies on the compiler knowing
58 As mentioned above, CFI is entirely compiler-based and therefore relies on
69 Current areas of QEMU that are not entirely compatible with CFI are:
/openbmc/linux/Documentation/devicetree/bindings/arm/
H A Dsecure.txt5 kernel) are not TrustZone aware and run entirely in either the Normal
30 world consumers (like kernels that run entirely in Secure) to simply
/openbmc/qemu/include/qemu/
H A Dbitops.h510 * lie entirely within the 32 bit word. It is valid to request that
529 * lie entirely within the 8 bit word. It is valid to request that
548 * lie entirely within the 16 bit word. It is valid to request that
567 * lie entirely within the 64 bit word. It is valid to request that
588 * entirely within the 32 bit word. It is valid to request that
613 * entirely within the 64 bit word. It is valid to request that
639 * ignored. The bit field must lie entirely within the 32 bit word.
665 * ignored. The bit field must lie entirely within the 64 bit word.
/openbmc/openbmc/meta-openembedded/meta-oe/licenses/
H A DUFL61 avoid use of the name of the Original Version or similar names entirely.
76 be distributed entirely under this licence, and must not be distributed
/openbmc/linux/drivers/misc/lkdtm/
H A Drodata.c3 * This includes functions that are meant to live entirely in .rodata
/openbmc/linux/drivers/media/usb/pvrusb2/
H A Dpvrusb2-devattr.h114 meaning is contained entirely within the driver and is
126 integer scheme id; its meaning is contained entirely within the
/openbmc/openbmc/meta-google/recipes-google/ncsi/files/
H A Dgbmc-ncsi-networkd-wait.target.in2 # phosphor-networkd entirely, but not wait forever for the non-existent
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DSymlinks3 freeware, written entirely by myself. The intent is to use
H A Dpython-ldap5 and "as is". All users of this free software are solely and entirely
/openbmc/linux/arch/x86/include/asm/
H A Duaccess_64.h70 * enable it, but not remove it entirely).
76 * In fact, we could probably remove the size check entirely, since
/openbmc/linux/arch/sparc/include/asm/
H A Dextable.h8 * modified, so it is entirely up to the continuation code to figure out
/openbmc/linux/include/asm-generic/
H A Dextable.h9 * modified, so it is entirely up to the continuation code to figure out
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-bus-iio-sps3019 Writing 0 disables periodical self cleaning entirely.
/openbmc/linux/arch/arm64/mm/
H A Dpageattr.c89 * Those are guaranteed to consist entirely of page mappings, and in change_memory_common()
92 * So check whether the [addr, addr + size) interval is entirely in change_memory_common()
/openbmc/phosphor-host-ipmid/docs/
H A Dcontributing.md65 output is appreciated. If the change can be validated entirely by running unit
100 If you feel your patch has been missed entirely, of course it's alright to email
/openbmc/linux/arch/arm64/include/asm/
H A Dasm-prototypes.h28 * this prototype is not entirely accurate.
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/qad/
H A Dqad_git.bb6 for tasks to be carried out entirely automatically."
/openbmc/linux/tools/perf/tests/workloads/
H A Ddatasym.c25 * and store instructions to be skipped entirely. This in datasym()
/openbmc/openbmc/poky/meta/recipes-core/glibc/
H A Dglibc-tests.inc25 # makefiles don't clean entirely (and also sometimes fails due to too many args)
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libgpiod/libgpiod-1.x/
H A D0001-bindings-cxx-disable-tests.patch8 the project, just disable C++ tests entirely.
/openbmc/linux/include/drm/
H A Ddrm_mm.h153 * entirely opaque and should only be accessed through the provided funcions.
154 * Since allocation of these nodes is entirely handled by the driver they can be
187 * entirely opaque and should only be accessed through the provided functions
223 * drm_mm_scan_remove_block(). The structure is entirely opaque and should only
/openbmc/linux/Documentation/process/
H A Ddeprecated.rst10 some deprecated API into the new API and entirely remove the old API in
40 destabilize a system or entirely break it, which makes it impossible
178 itself is important. Maybe it should be removed entirely?
270 the array declaration entirely::

12345678910>>...33