Searched refs:stable (Results 1 – 22 of 22) sorted by relevance
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 #
127 bool stable = (fabs(coefs[4]) < 1.0f && fabs(coefs[3]) < 1.0f + coefs[4]); in setCoefficients() local137 return stable; in setCoefficients()
87 // ABI-stable.168 // ABI-stable.
5 external/kernel-headers has the headers from the stable kernel tree which is generally
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
44 // enumerate stable entry points for APEX use
76 - The stable API exposed to nanoapps127 ``core``. This code must have a stable way to access the platform-specific128 implementation of the common platform API. This is handled by providing a stable
51 # to the default namespace. This is possible since their ABI is stable across
72 // Convenience build target for the version of the netd stable AIDL interface used by the platform.
330 # 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
418 # Using Sysprop as API. So the ro.surface_flinger.* are guaranteed to be API-stable
327 # Allow dumpstate to talk to these stable AIDL services over binder
218 # This directory is considered to be a VNDK-stable655 # Vendor apps are permited to use only stable public services. If they were to use arbitrary715 # to obtain an already established socket via some public/official/stable API and then exchange845 # These functions are considered vndk-stable and thus must be allowed for
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
380 # 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