| commit | c83d3e4b72f8f25bbac39a577f125f0ca04354da | [log] [tgz] |
|---|---|---|
| author | Christopher Tate <ctate@google.com> | Wed Feb 04 13:48:29 2015 -0800 |
| committer | Christopher Tate <ctate@google.com> | Wed Feb 04 13:48:29 2015 -0800 |
| tree | 858c34afea9778571d61fd2f92e22fa7029181f7 | |
| parent | d7310bd1499c0b48594a8fbbcbe0c7e80c1e5832 [diff] |
Always re-establish kernel alarms when considering new alarm set As a backstop against missed alarm delivery / wakeups or clock slew, make sure to always schedule a kernel alarm for the next alarm events of interest when we've reexamined the set of deliverable alarms. Bug 19201933 Change-Id: I3cd37a63dfb0c8258941497d4ba516ed00e2edad