Searched full:explicitely (Results 1 – 13 of 13) sorted by relevance
260 * Explicitely check for the capability mode to avoid in __vdso_init_hpet()
40 * in RFC 7091 and draft-deremin-rfc4491-bis. While in ISO/IEC 14888-3 it is explicitely asked
34 * in RFC 7091 and draft-deremin-rfc4491-bis. While in ISO/IEC 14888-3 it is explicitely asked
589 // unless explicitely disabled in createHexagonMCSubtargetInfo()
697 /* Always explicitely set forwarding to on or off for now */ in wpa_supplicant_join_mesh()
777 // Do only verify regions if explicitely activated using EXPENSIVE_CHECKS or
1645 * if we're explicitely requested to ignore PPS data. in process_pps()
33 * types, explicitely using two's complement arithmetics where
763 # in RFC 7091 and draft-deremin-rfc4491-bis. While in ISO/IEC 14888-3 it is explicitely asked
5039 but allow to explicitely enable it.
3921 * in RFC 7091 and draft-deremin-rfc4491-bis. While in ISO/IEC 14888-3 it is explicitely asked
13422 - set basedate based on build stamp if not set explicitely22367 - PPS-HACK works again; now controllable (explicitely) by the env var PPSAPI_HACK=true/yes/1 (anything else is NO)24373 - Require SHA1 explicitely, to avoid confusion with (deprecated) SHA0.27851 - check the return value of 'more_pkt()' when used in iterations, or trash it explicitely28307 - Avoid endless loop by logging only the first 5 errors explicitely, counting the next 10 silently, and aborting[all...]