Thread (5 messages) 5 messages, 3 authors, 2012-10-24

Re: drivers/cpufreq/cpufreq_governor.c:46:53: sparse: incorrect type in argument 2 (different modifiers)

From: Viresh Kumar <viresh.kumar@linaro.org>
Date: 2012-10-24 06:35:13

On 24 October 2012 06:03, Rafael J. Wysocki [off-list ref] wrote:
On Tuesday 23 of October 2012 10:55:51 Viresh Kumar wrote:
quoted
@Rafael: Most of these are due to mixed use of u64 and cputime64_t. Both of
which are u64 if i am not wrong. Any specific reason that we used cputime64_t
instead of u64? Or can i make everything u64 instead in governors?
Well, there might be a reason in the past, but I'm not sure it's still there. :-)

I _think_ you can use u64 everywhere.  It would be more correct than the current
situation anyway.
Great. I will send another set for these warnings..

--
viresh
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help