Searched refs:many (Results 1 – 25 of 41) sorted by relevance
12
| /system/bpf/ |
| D | Android.bp | 17 // Disabling due to many unavoidable warnings from POSIX API usage.
|
| /system/chre/chre_api/legacy/v1_2/chre/ |
| D | sensor_types.h | 188 #error Too many sensor types
|
| D | sensor.h | 252 #error Too many sensor events.
|
| /system/netd/ |
| D | Android.bp | 29 "-google-runtime-int", // Too many unavoidable warnings due to strtol()
|
| /system/chre/chre_api/include/chre_api/chre/ |
| D | sensor_types.h | 204 #error Too many sensor types
|
| D | sensor.h | 366 #error Too many sensor events.
|
| /system/update_engine/ |
| D | pylintrc | 82 # We leave many of the style warnings to judgement/peer review.
90 too-many-arguments,
91 too-many-branches,
92 too-many-instance-attributes,
93 too-many-lines,
94 too-many-locals,
95 too-many-public-methods,
96 too-many-return-statements,
97 too-many-statements,
|
| D | update_metadata.proto | 122 // many signatures to support many different types of client. Then client
|
| /system/chre/chre_api/legacy/v1_0/chre/ |
| D | sensor.h | 278 #error Too many sensor events.
|
| /system/bt/build/ |
| D | Android.bp | 40 // there are too many unused parameters in all the code.
|
| /system/chre/chre_api/legacy/v1_1/chre/ |
| D | sensor.h | 394 #error Too many sensor events.
|
| /system/core/libmemunreachable/tests/ |
| D | Allocator_test.cpp | 62 TEST_F(AllocatorTest, many) { in TEST_F() argument
|
| /system/extras/ioshark/ |
| D | README | 28 will launch as many threads as there are input files, so 1 thread/file.
|
| /system/extras/app-launcher/ |
| D | README | 4 Introduction: app-launcher is a script that launches apps many times,
|
| /system/extras/simpleperf/doc/ |
| D | inferno.md | 63 You can select how long to sample for, the color of the node and many other
|
| /system/tools/hidl/c2hal/ |
| D | c2hal_l.ll | 254 // this is so frowned upon on so many levels, but here vars are so that we can
|
| /system/update_engine/update_engine/ |
| D | update_metadata.proto | 122 // many signatures to support many different types of client. Then client
|
| /system/sepolicy/prebuilts/api/26.0/private/ |
| D | app_neverallows.te | 126 # currently does not expose caller UID information and, even if it did, many
|
| /system/core/liblog/ |
| D | README.md | 166 new message can get through indicating how many messages were dropped as a result. Please take
|
| /system/sepolicy/prebuilts/api/27.0/private/ |
| D | app_neverallows.te | 131 # currently does not expose caller UID information and, even if it did, many
|
| /system/sepolicy/prebuilts/api/29.0/public/ |
| D | attributes | 239 # Unlike phone, in a car many modules are external from Android perspective and
|
| /system/sepolicy/public/ |
| D | attributes | 239 # Unlike phone, in a car many modules are external from Android perspective and
|
| /system/sepolicy/prebuilts/api/28.0/public/ |
| D | attributes | 223 # Unlike phone, in a car many modules are external from Android perspective and
|
| /system/sepolicy/prebuilts/api/28.0/private/ |
| D | app_neverallows.te | 154 # currently does not expose caller UID information and, even if it did, many
|
| /system/chre/ |
| D | README.md | 190 There are many well-established coding standards within Google. The official
|
12