Searched refs:have (Results 1 – 25 of 429) sorted by relevance
12345678910>>...18
| /system/sepolicy/prebuilts/api/26.0/private/ |
| D | postinstall_dexopt.te | 4 # We have to manually transition, as we don't have an entrypoint.
|
| /system/sepolicy/prebuilts/api/27.0/private/ |
| D | postinstall_dexopt.te | 4 # We have to manually transition, as we don't have an entrypoint.
|
| /system/sepolicy/prebuilts/api/28.0/private/ |
| D | postinstall_dexopt.te | 4 # We have to manually transition, as we don't have an entrypoint.
|
| /system/sepolicy/private/compat/30.0/ |
| D | 30.0.ignore.cil | 1 ;; new_objects - a collection of types that have been introduced that have no
|
| /system/sepolicy/prebuilts/api/28.0/public/ |
| D | hal_neverallows.te | 1 # only HALs responsible for network hardware should have privileged
14 # NOTE: HALs for automotive devices have an exemption from this rule because in
15 # a car it is common to have external modules and HALs need to communicate to
30 # have multiple HALs in it (or even all of them) with the subsequent policy of
|
| /system/sepolicy/public/ |
| D | hal_neverallows.te | 1 # only HALs responsible for network hardware should have privileged
15 # NOTE: HALs for automotive devices have an exemption from this rule because in
16 # a car it is common to have external modules and HALs need to communicate to
32 # have multiple HALs in it (or even all of them) with the subsequent policy of
|
| /system/sepolicy/prebuilts/api/29.0/public/ |
| D | hal_neverallows.te | 1 # only HALs responsible for network hardware should have privileged
14 # NOTE: HALs for automotive devices have an exemption from this rule because in
15 # a car it is common to have external modules and HALs need to communicate to
30 # have multiple HALs in it (or even all of them) with the subsequent policy of
|
| D | flags_health_check.te | 24 # configurable flags have been reset during booting. Mistakenly modified by unrelated components can
29 # have been reset during current booting. Mistakenly modified by unrelated components can
|
| /system/sepolicy/prebuilts/api/30.0/public/ |
| D | hal_neverallows.te | 1 # only HALs responsible for network hardware should have privileged
15 # NOTE: HALs for automotive devices have an exemption from this rule because in
16 # a car it is common to have external modules and HALs need to communicate to
32 # have multiple HALs in it (or even all of them) with the subsequent policy of
|
| D | flags_health_check.te | 28 # configurable flags have been reset during booting. Mistakenly modified by unrelated components can
33 # have been reset during current booting. Mistakenly modified by unrelated components can
|
| /system/chre/apps/chqts/src/ |
| D | Android.bp | 15 // While it's arguably overkill to have unit test for our testing code,
17 // difficult to test. To the extent that we have platform-independent
18 // code here, it seems a long-term time saver to have Linux tests for
|
| /system/sepolicy/prebuilts/api/27.0/private/compat/26.0/ |
| D | 26.0.ignore.cil | 1 ;; new_objects - a collection of types that have been introduced that have no
|
| /system/libbase/ |
| D | README.md | 13 the ideal is to have both.
19 If you have a routine that's really useful in your project,
38 Code here is also expected to have good test coverage.
|
| /system/sepolicy/prebuilts/api/30.0/private/compat/29.0/ |
| D | 29.0.ignore.cil | 1 ;; new_objects - a collection of types that have been introduced that have no
|
| /system/sepolicy/private/compat/29.0/ |
| D | 29.0.ignore.cil | 1 ;; new_objects - a collection of types that have been introduced that have no
|
| /system/sepolicy/prebuilts/api/30.0/private/ |
| D | rs.te | 1 # Any files which would have been created as app_data_file
32 # rs can access app data, so ensure it can only be entered via an app domain and cannot have
|
| D | boringssl_self_test.te | 14 # Due to build skew, the version of libcrypto in /vendor may have a different hash than
16 # which also have permission to write to the same files in /dev/boringssl. In the case where
17 # vendor and system libcrypto have the same hash, there will be a race to create the file,
40 # Marker files, common to both domains, indicating KAT have been performed on a particular libcrypto
|
| /system/sepolicy/prebuilts/api/29.0/private/ |
| D | rs.te | 1 # Any files which would have been created as app_data_file
32 # rs can access app data, so ensure it can only be entered via an app domain and cannot have
|
| /system/sepolicy/private/ |
| D | rs.te | 1 # Any files which would have been created as app_data_file
32 # rs can access app data, so ensure it can only be entered via an app domain and cannot have
|
| D | boringssl_self_test.te | 14 # Due to build skew, the version of libcrypto in /vendor may have a different hash than
16 # which also have permission to write to the same files in /dev/boringssl. In the case where
17 # vendor and system libcrypto have the same hash, there will be a race to create the file,
40 # Marker files, common to both domains, indicating KAT have been performed on a particular libcrypto
|
| /system/core/janitors/ |
| D | OWNERS | 1 # OWNERS file for projects that don't really have owners so much as volunteer janitors.
|
| /system/sepolicy/prebuilts/api/30.0/private/compat/28.0/ |
| D | 28.0.ignore.cil | 1 ;; new_objects - a collection of types that have been introduced that have no
|
| /system/libhidl/transport/allocator/1.0/ |
| D | IAllocator.hal | 25 * Return memory must have instance name corresponding to this type of memory.
34 * Return memory must have instance name corresponding to this type of memory.
|
| /system/sepolicy/private/compat/28.0/ |
| D | 28.0.ignore.cil | 1 ;; new_objects - a collection of types that have been introduced that have no
|
| /system/sepolicy/prebuilts/api/28.0/private/compat/27.0/ |
| D | 27.0.ignore.cil | 1 ;; new_objects - a collection of types that have been introduced that have no
|
12345678910>>...18