Messages in this thread | | | Date | Mon, 24 Oct 2011 10:08:32 +0200 | From | Martin Schwidefsky <> | Subject | Re: Linux 3.1-rc9 |
| |
On Mon, 24 Oct 2011 09:51:09 +0200 Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Mon, Oct 24, 2011 at 9:48 AM, Martin Schwidefsky > <schwidefsky@de.ibm.com> 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.
Ok, cool. In that case I'll cook up a patch without cputime_t & cputime64_t and put it on the cputime branch on git390.
-- blue skies, Martin.
"Reality continues to ruin my life." - Calvin.
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |