clarify a usage constraint for cnt32_to_63()
authorNicolas Pitre <nico@fluxnic.net>
Mon, 20 Dec 2010 05:29:32 +0000 (00:29 -0500)
committerLinus Torvalds <torvalds@linux-foundation.org>
Mon, 20 Dec 2010 17:07:35 +0000 (09:07 -0800)
commitb8da46d3d55807037b58f14621a0949f18053bde
tree6c3e9f15d0002b571194e0330b0c381b534c61b2
parentde5e9d58200aafea4a33abcadcd12eb69eaba5c4
clarify a usage constraint for cnt32_to_63()

The cnt32_to_63 algorithm relies on proper counter data evaluation
ordering to work properly. This was missing from the provided
documentation.

Let's augment the documentation with the missing usage constraint and
fix the only instance that got it wrong.

Signed-off-by: Nicolas Pitre <nico@fluxnic.net>
Acked-by: David Howells <dhowells@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
arch/mn10300/kernel/time.c
include/linux/cnt32_to_63.h