On Mon, Oct 24, 2011 at 9:48 AM, Martin Schwidefsky
[off-list ref] wrote:

These types are still there because cputime_t can be u32 or u64. E.g. this

 timer->expires.cpu = 0;

will give the following sparse warning

 kernel/posix-cpu-timers.c:463:46: warning: implicit cast to nocast type

Ok, we should probably special-case zero for that case too (we
consider zero to be very special - it's not only the NULL pointer, but
0 is special for the bitwise types etc). So this is very arguably a
sparse issue: casting zero is special.

                  Linus