[lkml]   [2015]   [Apr]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch 02/39] hrtimer: Get rid of the resolution field in hrtimer_clock_base
On Wed, Apr 15, 2015 at 8:29 AM, Frans Klaver <> wrote:
> On Tue, Apr 14, 2015 at 11:08 PM, Thomas Gleixner <> wrote:
>> The field has no value because all clock bases have the same
>> resolution. The resolution only changes when we switch to high
>> resolution timer mode. We can evaluate that from a single static
>> variable as well. In the !HIGHRES case its simply a constant.
>> Export the variable, so we can simplify the usage sites.
> There seems to be only one usage site outside hrtimer.c itself. That
> one only reads the value.

OK, this is incorrect. Still, if it's only meant to be read from
outside hrtimer.c:

> Wouldn't it make sense to keep the variable
> from the interface and use a read function instead?


 \ /
  Last update: 2015-04-15 09:01    [W:0.119 / U:0.168 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site