| /Linux-v5.4/drivers/rtc/ |
| D | rtc-ds1742.c | 84 unsigned int year, month, day, hour, minute, second, week; in ds1742_rtc_read_time() local
96 week = readb(ioaddr + RTC_DAY) & RTC_DAY_MASK; in ds1742_rtc_read_time()
105 tm->tm_wday = bcd2bin(week); in ds1742_rtc_read_time()
|
| D | rtc-bd70528.c | 28 u8 week; member
177 r->week &= ~BD70528_MASK_RTC_WEEK; in tm2rtc()
191 r->week |= bin2bcd(t->tm_wday); in tm2rtc()
213 t->tm_wday = bcd2bin(r->week & BD70528_MASK_RTC_WEEK); in rtc2tm()
|
| D | rtc-stk17ta8.c | 98 unsigned int year, month, day, hour, minute, second, week; in stk17ta8_rtc_read_time() local
113 week = readb(ioaddr + RTC_DAY) & RTC_DAY_MASK; in stk17ta8_rtc_read_time()
122 tm->tm_wday = bcd2bin(week); in stk17ta8_rtc_read_time()
|
| D | rtc-ds1553.c | 99 unsigned int year, month, day, hour, minute, second, week; in ds1553_rtc_read_time() local
111 week = readb(ioaddr + RTC_DAY) & RTC_DAY_MASK; in ds1553_rtc_read_time()
120 tm->tm_wday = bcd2bin(week); in ds1553_rtc_read_time()
|
| D | rtc-ds3232.c | 103 unsigned int week, twelve_hr, am_pm; in ds3232_read_time() local
113 week = buf[3]; in ds3232_read_time()
139 time->tm_wday = bcd2bin(week) - 1; in ds3232_read_time()
|
| /Linux-v5.4/Documentation/networking/ |
| D | netdev-FAQ.rst | 44 two week "merge window" where the main maintainers feed their new stuff
48 expected. After roughly a week of collecting fixes to the rc1 content,
51 state of churn), and a week after the last vX.Y-rcN was done, the
54 Relating that to netdev: At the beginning of the 2-week merge window,
91 the dev cycle. If it was tagged rc7 a week ago, then a release is
|
| /Linux-v5.4/Documentation/EDID/ |
| D | edid.S | 72 week: .byte WEEK label
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | reporting-bugs.rst | 161 they may not be able to address your bug in a day, a week, or two weeks.
171 have a high priority bug, please wait at least a week after the first bug
|
| /Linux-v5.4/drivers/video/fbdev/core/ |
| D | fbmon.c | 303 specs->week = block[8]; in parse_vendor_block()
307 DPRINTK(" Year: %u Week %u\n", specs->year, specs->week); in parse_vendor_block()
|
| /Linux-v5.4/include/linux/ |
| D | fb.h | 74 __u32 week; /* Week Manufactured */ member
|
| /Linux-v5.4/Documentation/arm/ |
| D | arm.rst | 146 last week :-)
|
| /Linux-v5.4/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 203 at the end of the week. In some cases pull requests could additionally
204 come also in the middle of the week depending on the current patch
|
| /Linux-v5.4/Documentation/networking/device_drivers/3com/ |
| D | vortex.txt | 445 end up working on this problem for a week or more as the maintainer
|
| /Linux-v5.4/Documentation/scsi/ |
| D | aic7xxx.txt | 335 408-957-2550, 24 hours a day, 7 days a week.
|
| D | aic79xx.txt | 438 408-957-2550, 24 hours a day, 7 days a week.
|
| /Linux-v5.4/Documentation/process/ |
| D | kernel-docs.rst | 568 produced during the week. Published every Thursday.
|
| D | submitting-patches.rst | 402 receive comments within a week or so; if that does not happen, make sure
404 one week before resubmitting or pinging reviewers - possibly longer during
|
| D | 2.Process.rst | 68 time. Linus releases new -rc kernels about once a week; a normal series
|
| D | howto.rst | 268 release a new -rc kernel every week.
|
| /Linux-v5.4/Documentation/virt/kvm/ |
| D | timekeeping.txt | 214 06h byte Current day of week (BCD)
|
| /Linux-v5.4/ |
| D | CREDITS | 3667 D: One-week tutorials on Linux twice a year (free of charge)
|
