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

On 25 October 2012 02:44, Rafael J. Wysocki [off-list ref] wrote:

On Wednesday 24 of October 2012 13:15:58 Viresh Kumar wrote:

quoted

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 <redacted>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>

This series appears to be based on your "cpufreq: governors: remove
redundant code" patch that hasn't been applied yet.

Please rebase it on top of linux-pm/linux-next or on top of v3.7-rc2,
whichever is more convenient, and resend.

Please apply it after applying the latest cpufreq: governors patch i have sent.

--
viresh