I see that find_next_zero_bit() has a first arg of void* in about half
of the archs and unsigned long* in the rest (incl asm-i386/bitops.h).
Looking at incompatable pointer type warnings in a recent compile, I
found one where the caller was passing a u64*, thus the error.
Should all of the archs use a void* for this, or is there some reason
not to?
test_and_set_bit() and test_and_clear_bit() also have the same issue.
-JimC
-
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/
This archive was generated by hypermail 2b29 : Sun Dec 15 2002 - 22:00:20 EST