Searched refs:have (Results 1 – 25 of 552) sorted by relevance
12345678910>>...23
1 ;; new_objects - a collection of types that have been introduced with ToT policy2 ;; that have no analogue in 202404 policy. Thus, we do not need to map these types to
1 ;; new_objects - a collection of types that have been introduced with ToT policy2 ;; that have no analogue in 31.0 policy. Thus, we do not need to map
1 ;; new_objects - a collection of types that have been introduced with ToT policy2 ;; that have no analogue in 34.0 policy. Thus, we do not need to map these types to
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-independent18 // code here, it seems a long-term time saver to have Linux tests for
1 ;; new_objects - a collection of types that have been introduced with ToT policy2 ;; that have no analogue in 32.0 policy. Thus, we do not need to map
1 ;; new_objects - a collection of types that have been introduced with ToT policy2 ;; that have no analogue in 33.0 policy. Thus, we do not need to map
1 # only HALs responsible for network hardware should have privileged19 # NOTE: HALs for automotive devices have an exemption from this rule because in20 # a car it is common to have external modules and HALs need to communicate to65 # have multiple HALs in it (or even all of them) with the subsequent policy of
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.
5 #error TODO(b/111362593) parcelables do not have headers
5 #error TODO(b/111362593) parcelables do not have bn classes
5 #error TODO(b/111362593) enums do not have bp classes
5 #error TODO(b/111362593) defined_types do not have bp classes
5 #error TODO(b/111362593) defined_types do not have bn classes
5 #error TODO(b/111362593) enums do not have bn classes