Hi,

currently arch/mn10300/include/asm/atomic.h and include/asm-generic/atomic.h 
warns right before atomic_read/atomic_set/atomic_add_return/ atomic_sub_return 
that atomic_t only guarantees a useful range of 24 bits. 
Documentation/atomic_ops.txt informs about the historical reason why this was 
true for 32-bit Sparc - something that was changes in linux 2.6.3 using a hash 
array with spinlocks [1].

Is it save to assume that atomic_t provides us the full range of 32 bit after 
2.6.3 and can those statements in both atomic.h be removed?

Kind regards,
	Sven Eckelmann

[1] http://lwn.net/Articles/71732/
[unhandled content-type:application/pgp-signature]