Re: [PATCH 1/2] cpufreq: Fix sparse warnings by updating cputime64_t to u64

2012-10-25 Thread Rafael J. Wysocki
On Thursday, October 25, 2012 09:00:22 AM Viresh Kumar wrote: > On 25 October 2012 02:44, Rafael J. Wysocki wrote: > > On Wednesday 24 of October 2012 13:15:58 Viresh Kumar wrote: > >> There were few sparse warnings due to mismatch of type on function > >> arguments. > >> Two types were used u64

Re: [PATCH 1/2] cpufreq: Fix sparse warnings by updating cputime64_t to u64

2012-10-24 Thread Viresh Kumar
On 25 October 2012 02:44, Rafael J. Wysocki wrote: > On Wednesday 24 of October 2012 13:15:58 Viresh Kumar wrote: >> There were few sparse warnings due to mismatch of type on function arguments. >> Two types were used u64 and cputime64_t. Both are actually u64, so use u64 >> only. >> >> Reported-

Re: [PATCH 1/2] cpufreq: Fix sparse warnings by updating cputime64_t to u64

2012-10-24 Thread Rafael J. Wysocki
On Wednesday 24 of October 2012 13:15:58 Viresh Kumar wrote: > There were few sparse warnings due to mismatch of type on function arguments. > Two types were used u64 and cputime64_t. Both are actually u64, so use u64 > only. > > Reported-by: Fengguang Wu > Signed-off-by: Viresh Kumar This ser

[PATCH 1/2] cpufreq: Fix sparse warnings by updating cputime64_t to u64

2012-10-24 Thread Viresh Kumar
There were few sparse warnings due to mismatch of type on function arguments. Two types were used u64 and cputime64_t. Both are actually u64, so use u64 only. Reported-by: Fengguang Wu Signed-off-by: Viresh Kumar --- This solution was discussed here: http://www.mail-archive.com/linaro-dev@list