Searched refs:future (Results 1 – 25 of 110) sorted by relevance
12345
55 for (GceFuture<?> future: futures) { in schedule()56 mFutures.add(future); in schedule()65 for (GceFuture<?> future : mFutures) { in schedule()69 future.get( in schedule()73 stragglers.add(future); in schedule()78 stragglers.add(future); in schedule()
62 static PyObject *future; in future_parse() local63 if (!future) { in future_parse()64 future = PyString_InternFromString("__future__"); in future_parse()65 if (!future) in future_parse()95 if (s->v.ImportFrom.module == future) { in future_parse()
18 …e computer's TPM (Trusted Platform Module) without asking for user confirmation in the future.\n\n"34 #string TPM_NO_PPI_INFO #language en-US "to approve future Operating System reques…38 …tion does not clear the TPM, but by approving this configuration change, future actions to clear t…43 …P_CHANGE_PCRS_FALSE #language en-US "WARNING: Allowing future changes to format …44 …P_CHANGE_EPS_FALSE_1 #language en-US "WARNING: Allowing future changes to the TPM…49 …uested to allow the Operating System to %s without asking for user confirmation in the future.\n\n"55 #string TCG_STORAGE_NO_PPI_INFO #language en-US "to approve future Operating Syste…
18 …e computer's TPM (Trusted Platform Module) without asking for user confirmation in the future.\n\n"26 #string TPM_NO_PPI_INFO #language en-US "to approve future Operating System reques…29 …tion does not clear the TPM, but by approving this configuration change, future actions to clear t…
19 LOCAL_MODULE := gralloc.cutf_ivsh-future
19 LOCAL_MODULE := hwcomposer.cutf_ivsh-future
8 schema may change in the future. It differs somewhat from the early versions
19 …e computer's TPM (Trusted Platform Module) without asking for user confirmation in the future.\n\n"44 #string TPM_NO_PPI_INFO #language en-US "to approve future Operating System reques…52 …tion does not clear the TPM, but by approving this configuration change, future actions to clear t…
2 possibly other modules, in a not too distant future).
5 # timer service. In the future, the Thread creation should possibly be
7 // be recorded in the data hub for future processing.Ot her data contributed to the data hub might38 …der. As an example, progress codes might be recorded in the data hub for future processing. For ex…
7 # be recorded in the data hub for future processing.Ot her data contributed to the data hub might
389 def _getdate(future=0, weekdayname=_weekdayname, monthname=_monthname): argument392 year, month, day, hh, mm, ss, wd, y, z = gmtime(now + future)
46 com.android.future.usb.accessory \
494 future = time2netscape(time.time()+3600)496 future)509 future)511 future)514 'expires=%s; max-age=0' % future)516 'max-age=0; expires=%s' % future)
21 system/framework/com.android.future.usb.accessory.jar \
33 …vendor/qcom/sargo/proprietary/com.android.future.usb.accessory.jar:system/framework/com.android.fu…
33 …vendor/qcom/bonito/proprietary/com.android.future.usb.accessory.jar:system/framework/com.android.f…
112 Looking towards the future, a graphical user-interface is in the118 called "parser exception handling" in a near future release.
50 Processor-M, Intel Pentium M Processor, or any other future Intel
61 Fast 5-47 Reserved for future use268 The ``cookie`` parameter to the handler is reserved for future use and can be283 future, there could be additional such sub-services in the Standard calls
235 registered on per-level basis. This enables support for future CPUs that323 Service that may be added in the future.383 This limitation will enable future enhancements without having to510 the PSCI ``SYSTEM_OFF`` API. This issue will be fixed in a future version of580 adding future extensions.661 the PSCI ``SYSTEM_OFF`` API. This issue will be fixed in a future version of813 absent. These issues will be addressed in future releases.822 the PSCI ``SYSTEM_OFF`` API. This issue will be fixed in a future version of995 release. A future kernel version will re-enable these features.1083 more future proof.[all …]
92 # Any undefined BITs are reserved for future use.<BR>