Searched refs:stable (Results 1 – 25 of 25) sorted by relevance
5 external/kernel-headers has the headers from the stable kernel tree which is generally12 Last update from kernel branch: `upstream-f2fs-stable-linux-5.10.y`
2 # ERROR: Modification detected of stable AIDL API file #
142 // It does not have a stable interface.155 // It does not have a stable interface.165 // It does not have a stable interface.
213 int stable = params_.GetChannelIndex("stable-channel"); in TEST_F() local216 EXPECT_LE(beta, stable); in TEST_F()
127 CHROMEOS_RELEASE_DESCRIPTION=6946.63.0 (Official Build) stable-channel link130 CHROMEOS_RELEASE_TRACK=stable-channel
52 // Now That Keystore 2.0 has a vintf stable interface this library is
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
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
329 # Allow dumpstate to talk to these stable AIDL services over binder
207 # This directory is considered to be a VNDK-stable648 # Vendor apps are permited to use only stable public services. If they were to use arbitrary708 # to obtain an already established socket via some public/official/stable API and then exchange838 # These functions are considered vndk-stable and thus must be allowed for
422 # Using Sysprop as API. So the ro.surface_flinger.* are guaranteed to be API-stable
343 # Allow dumpstate to talk to these stable AIDL services over binder
226 # This directory is considered to be a VNDK-stable659 # Vendor apps are permited to use only stable public services. If they were to use arbitrary727 # to obtain an already established socket via some public/official/stable API and then exchange841 # These functions are considered vndk-stable and thus must be allowed for
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
382 # 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.
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
91 However, if a transitive dependency has a stable ABI, it is not included93 Currently (2019/08/05), the only module type that can provide stable ABI is
140 can be updated depends on the platform and how stable the interfaces for the