x86, atomic: atomic64_read() take a const pointer
authorH. Peter Anvin <hpa@zytor.com>
Tue, 10 Jan 2012 03:33:24 +0000 (19:33 -0800)
committerH. Peter Anvin <hpa@zytor.com>
Tue, 10 Jan 2012 03:33:24 +0000 (19:33 -0800)
commit8030c36d13f030103356709e63638678fdc66fdc
treef50b2e91261697914ab8ff4745b3a862f3a275e0
parentda517a08ac5913cd80ce3507cddd00f2a091b13c
x86, atomic: atomic64_read() take a const pointer

atomic64_read() doesn't actually write anything (as far as the C
environment is concerned... the CPU does actually write but that's an
implementation quirk), so it should take a const pointer.

This does NOT mean that it is safe to use atomic64_read() on an object
in readonly storage (it will trap!)

Reported-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
Link: http://lkml.kernel.org/r/20120109165859.1879abda.akpm@linux-foundation.org
arch/x86/include/asm/atomic64_32.h