diff options
| author | H. Peter Anvin <hpa@zytor.com> | 2012-01-09 19:33:24 -0800 |
|---|---|---|
| committer | H. Peter Anvin <hpa@zytor.com> | 2012-01-09 19:33:24 -0800 |
| commit | 8030c36d13f030103356709e63638678fdc66fdc (patch) | |
| tree | f50b2e91261697914ab8ff4745b3a862f3a275e0 /arch/x86/kernel | |
| parent | da517a08ac5913cd80ce3507cddd00f2a091b13c (diff) | |
| download | linux-8030c36d13f030103356709e63638678fdc66fdc.tar.bz2 | |
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
Diffstat (limited to 'arch/x86/kernel')
0 files changed, 0 insertions, 0 deletions