From: Andi Kleen <ak@muc.de>
Date: Tue, 15 Apr 2003 13:24:30 +0200
I worked around this by declaring a new data type atomic_bitmask32
with matching set_bit32/clear_bit32 etc. interfaces. Currently only
on x86-64 aomitc_bitmask32 is defined to unsigned, everybody else
still uses unsigned long. The other 64bit architectures can define it to
unsigned too if they can confirm that it's ok to do.
I have no problem with this.
If you are clever, you can define a generic version even for the
"unsigned long" 64-bit platforms. It's left as an exercise to
the reader :-)
-
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 : Wed Apr 23 2003 - 22:00:18 EST