On Mon, 2007-05-14 at 11:58 -0700, Andrew Morton wrote:
> Urgh, that was probably me trying to manage the maelstrom from a million
> monkeys mucking in the same code for multiple months, sigh.
>
> So what do "broke" and "fix" mean in this context? What are the
> consequences of this bug, and of its fix? Is the above appropriate for
> 2.6.21.x and if so why?
clocksource_resume() is not called except from
unregister_time_interpolator(), which is definitely the wrong place.
No 2.6.21.x material, as the move of the timekeeping code happened after
2.6.21.
tglx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
