Home
last modified time | relevance | path

Searched refs:unlikely (Results 1 – 9 of 9) sorted by relevance

/rk3399_ARM-atf/include/export/
H A DREADME8 make name clashes with third-party code unlikely.
/rk3399_ARM-atf/include/drivers/nxp/crypto/caam/
H A Dsec_hw_specific.h25 #define unlikely(x) __builtin_expect(!!(x), 0) macro
/rk3399_ARM-atf/drivers/nxp/crypto/caam/src/
H A Dsec_hw_specific.c457 if (unlikely(sec_error_code) != 0) { in hw_poll_job_ring()
/rk3399_ARM-atf/docs/threat_model/
H A Dsupply_chain_threat_model.rst231 | | followed [9]_ making credential compromise unlikely. |
313 | | contributor is lower. However, even though unlikely, it |
355 | | their source repositories. Although unlikely, it is |
/rk3399_ARM-atf/docs/process/
H A Dcode-review-guidelines.rst170 instead." is usually not very helpful. The patch author is unlikely to
/rk3399_ARM-atf/docs/plat/
H A Drpi3.rst220 unlikely that the kernel image will fit in the space reserved for BL33 images.
/rk3399_ARM-atf/docs/about/
H A Dlts.rst163 Though we are unlikely to update CI scripts, but time to time migrating a newer
/rk3399_ARM-atf/docs/threat_model/firmware_threat_model/
H A Dthreat_model.rst263 that require physical access are unlikely in server environments while
/rk3399_ARM-atf/docs/design/
H A Dfirmware-design.rst1601 unlikely scenario where a CVE and an erratum numbers clash, the CVE number