On Fri, 2019-11-08 at 12:01 +0100, Toke Høiland-Jørgensen wrote: > > My reasoning for doing it this way was that we have another set of APIs > dealing with airtime which doesn't do any shifting; so keeping the APIs > in the same unit (straight airtime) seemed less confusing. Fair enough. > We could add (inline) setter and getter functions for the tx_time_est > field instead to avoid sprinkling shifts all over the place? :) It doesn't really bother me that much, but yeah, perhaps that's easier. johannes
