aboutsummaryrefslogtreecommitdiffstats
path: root/lib/timerqueue.c
diff options
context:
space:
mode:
authorH. Peter Anvin <[email protected]>2012-01-10 03:33:24 +0000
committerH. Peter Anvin <[email protected]>2012-01-10 03:33:24 +0000
commit8030c36d13f030103356709e63638678fdc66fdc (patch)
treef50b2e91261697914ab8ff4745b3a862f3a275e0 /lib/timerqueue.c
parentx86, UV: Update Boot messages for SGI UV2 platform (diff)
downloadkernel-8030c36d13f030103356709e63638678fdc66fdc.tar.gz
kernel-8030c36d13f030103356709e63638678fdc66fdc.zip
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 <[email protected]> Signed-off-by: H. Peter Anvin <[email protected]> Link: http://lkml.kernel.org/r/[email protected]
Diffstat (limited to 'lib/timerqueue.c')
0 files changed, 0 insertions, 0 deletions