Searched refs:stable (Results 1 – 25 of 26) sorted by relevance
12
114 // It does not have a stable interface.127 // It does not have a stable interface.137 // It does not have a stable interface.
2 # ERROR: Modification detected of stable AIDL API file #
30 "libcutils", // does not expose a stable C API59 // enumerate stable entry points for APEX use
5 external/kernel-headers has the headers from the stable kernel tree which is generally
87 // ABI-stable.169 // ABI-stable.
217 int stable = params_.GetChannelIndex("stable-channel"); in TEST_F() local220 EXPECT_LE(beta, stable); in TEST_F()
127 CHROMEOS_RELEASE_DESCRIPTION=6946.63.0 (Official Build) stable-channel link130 CHROMEOS_RELEASE_TRACK=stable-channel
45 // enumerate stable entry points for APEX use
66 - ``pal/``: The binary-stable Platform Abstraction Layer (PAL) C API definitions74 multiple platforms may choose to use the binary-stable PAL interface - this
51 # to the default namespace. This is possible since their ABI is stable across
71 // Convenience build target for the version of the netd stable AIDL interface used by the platform.
174 Note that the PAL APIs are binary-stable, in that it’s possible for the CHRE212 framework do not have a stable API.
117 should be globally unique and stable over time.
156 calling conventions must remain stable. It is not acceptable to require all
332 # Allow dumpstate to talk to these stable AIDL services over binder
211 # This directory is considered to be a VNDK-stable652 # Vendor apps are permited to use only stable public services. If they were to use arbitrary712 # to obtain an already established socket via some public/official/stable API and then exchange842 # These functions are considered vndk-stable and thus must be allowed for
426 # Using Sysprop as API. So the ro.surface_flinger.* are guaranteed to be API-stable
206 # This directory is considered to be a VNDK-stable647 # Vendor apps are permited to use only stable public services. If they were to use arbitrary713 # to obtain an already established socket via some public/official/stable API and then exchange851 # vndk-stable and thus must be allowed for all processes.
205 # This directory is considered to be a VNDK-stable653 # Vendor apps are permited to use only stable public services. If they were to use arbitrary719 # to obtain an already established socket via some public/official/stable API and then exchange858 # These functions are considered vndk-stable and thus must be allowed for
379 # Using Sysprop as API. So the ro.surface_flinger.* are guaranteed to be API-stable
150 # This directory is considered to be a VNDK-stable531 # Vendor apps are permited to use only stable public services. If they were to use arbitrary591 # to obtain an already established socket via some public/official/stable API and then exchange
150 # This directory is considered to be a VNDK-stable528 # Vendor apps are permited to use only stable public services. If they were to use arbitrary590 # to obtain an already established socket via some public/official/stable API and then exchange
136 type can be updated depends on the platform and how stable the interfaces for