Searched refs:likely (Results 1 – 25 of 27) sorted by relevance
12
/system/apex/tests/ |
D | README.md | 4 therefore will not likely succeed on a pure AOSP build.
|
/system/sepolicy/prebuilts/api/26.0/public/ |
D | update_engine_common.te | 36 # Access is also granted to proc:file, but it is likely unneeded
|
D | domain.te | 529 # services which can change any time framework/core is updated, breakage is likely. 803 # that, even assuming only non-buggy and non-malicious code, it is very likely
|
/system/libhidl/transport/manager/1.0/ |
D | IServiceManager.hal | 43 * WARNING: This function is for libhidl/HwBinder use only. You are likely 65 * WARNING: This function is for libhidl/HwBinder use only. You are likely
|
/system/sepolicy/prebuilts/api/27.0/public/ |
D | update_engine_common.te | 42 # Access is also granted to proc:file, but it is likely unneeded
|
D | domain.te | 532 # services which can change any time framework/core is updated, breakage is likely. 796 # that, even assuming only non-buggy and non-malicious code, it is very likely
|
/system/extras/libfec/ |
D | fec_private.h | 173 #define likely(x) __builtin_expect(!!(x), 1) macro
|
D | fec_read.cpp | 136 if (likely(interleaved < e->start) && !is_zero(f, interleaved)) { in __ecc_read() 332 if (likely(f->hashtree().check_block_hash_with_index(curr, data))) { in verity_read()
|
/system/chre/doc/ |
D | framework_testing.md | 13 platform-specific components likely aren’t compilable/available on a host
|
D | framework_overview.md | 112 1. Starting in platform-specific code, likely in a different thread, the
|
D | porting_guide.md | 29 words, this code is likely to be re-used by multiple platforms, but it is not
|
D | nanoapp_developer_guide.md | 339 Keep in mind that if one nanoapp encounters an assertion failure, it most likely
|
/system/bpf/bpfloader/ |
D | bpfloader.rc | 21 # Enable the eBPF JIT -- but do note that on 64-bit kernels it is likely
|
/system/extras/simpleperf/doc/ |
D | README.md | 122 3. Old Android versions are likely to be shipped with old kernels (< 3.18), 124 4. Old Android versions are likely to be shipped with Arm32 chips. In Arm32
|
/system/sepolicy/prebuilts/api/29.0/public/ |
D | property.te | 132 # likely that the policy is using r_file_perms directly instead of
|
D | domain.te | 654 # services which can change any time framework/core is updated, breakage is likely. 1099 # that, even assuming only non-buggy and non-malicious code, it is very likely
|
/system/core/libunwindstack/ |
D | AndroidVersions.md | 83 Since the new ops are not likely to be used very often, this allows
|
/system/sepolicy/prebuilts/api/30.0/public/ |
D | property.te | 299 # likely that the policy is using r_file_perms directly instead of
|
D | domain.te | 653 # services which can change any time framework/core is updated, breakage is likely. 1097 # that, even assuming only non-buggy and non-malicious code, it is very likely
|
/system/sepolicy/public/ |
D | property.te | 299 # likely that the policy is using r_file_perms directly instead of
|
D | domain.te | 653 # services which can change any time framework/core is updated, breakage is likely. 1097 # that, even assuming only non-buggy and non-malicious code, it is very likely
|
/system/extras/ioblame/ |
D | README | 85 the app/pid that did the original write (since the write most likely
|
/system/tools/aidl/docs/ |
D | aidl-cpp.md | 178 libnativehelper, although this is likely a transitive dependency of the other
|
/system/core/shell_and_utilities/ |
D | README.md | 29 and how usable it was likely to be.
|
/system/sepolicy/prebuilts/api/28.0/public/ |
D | domain.te | 648 # services which can change any time framework/core is updated, breakage is likely. 1100 # that, even assuming only non-buggy and non-malicious code, it is very likely
|
12