On 10/07/2014 08:48 AM, Noé RUBINSTEIN wrote: >> Sure, hwclock already has the ability to track the offset between the >> Hardware Clock and the System Clock(which presumably is the 'correct' time). > ...but this information is recorded only when setting the hardware > clock, which is impossible on some (arguably buggy) targets. Are you sure that drift factor (re)calculation does not happen if writing the Hardware Clock fails? I just had a quick look at the code and it seem that we do not test to see if write fails. So (re)calculation might work as is? -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
