Searched refs:years (Results 1 – 9 of 9) sorted by relevance
91 uchar min, date, month, years; in rtc_validate() local117 years = data[RTC_YEAR]; in rtc_validate()123 0x99 < years || 0x09 < (years & 0x0F) || in rtc_validate()126 ((0x00 != (years & 0x03)) || in rtc_validate()127 (0x00 == years && 0x00 != (data[RTC_MONTH] & 0xC0))))) { in rtc_validate()
493 'cros_bundle_firmware', which I wrote some years ago. That tool was based on495 years. In particular its handling of x86 images is convoluted.
462 <n>y = key expires in n years
143 years, to give any third party, for a charge no more than your
307 least three years, to give the same user the materials
286 least three years, to give the same user the materials
702 will be performed for both leap- and nonleap-years.
665 some years so this number can get quite high.
1624 commonly used some years ago: