> There's actually a real world case that's pretty common where we want > to work with dates before 2016. When I power cycle my device and it > totally loses battery, I notice that the firmware seems to start as: > > 2013-01-21 00:50:02 > > It's possible we could need to run for a while in this state and we > possibly could even need alarms to fire. ...but that's nowhere near > the problematic dates and presumably someone wouldn't have a system in > the "clock set totally wrong" state for a really long time.
Yeah... I don't think it really makes much sense to worry about that. At that point it's much more likely that you will loose an alarm because the user finally fixes the clock at some point (either manually or by connecting to a network and having some automated sync service jump in), and we never worry about something like that either. I mean, fixing it wouldn't be a big deal (another 5 lines or so maybe), but I just don't think it's worth adding any complexity. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
