time_monotonic_ms values did wrap every ~24 days, leading to problems
in code that did not cope with that. Instead of fixing all places where
relative comparisons with time_monotonic_ms() are made, just use a
bigger datatype. Convert all users to the new type.
Origin commit data
------------------
Branch: ni/coolstream
Commit: 99c8168d2c
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2017-09-23 (Sat, 23 Sep 2017)
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: e7c5d8925f
Author: [CST] Focus <focus.cst@gmail.com>
Date: 2012-03-05 (Mon, 05 Mar 2012)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
git-svn-id: file:///home/bas/coolstream_public_svn/THIRDPARTY/applications/neutrino-experimental@1251 e54a6e83-5905-42d5-8d5c-058d10e6a962
Origin commit data
------------------
Branch: ni/coolstream
Commit: 4f09c0c22a
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2011-03-06 (Sun, 06 Mar 2011)
------------------
This commit was generated by Migit