On Fri, 2016-11-11 at 17:37 +0100, Benjamin Beichler wrote: > Due to the cast from uint32_t to int64_t, a wrong next beacon timing > is > calculated and effectively the beacon timer stops to work. This is > especially bad for 802.11s mesh networks, because discovery breaks > without beacons. > Applied. Please note how I changed the commit subject, and use that scheme in the future.
johannes
