H. Peter Anvin wrote:
Jeff Garzik wrote:
Volatile is usually reserved for a specific need on a specific arch.
I doubt it is correct to force it on all arches.
They already are volatile; the issue is adding "const".
All io(read|write)* pointers are volatile, IIRC.
No, none are volatile, hence my comment.
[EMAIL PROTECTED] linux-2.6]$ grep volatile lib/iomap.c include/asm-generic/iomap.h
[EMAIL PROTECTED] linux-2.6]$
Maybe you were thinking about writel() and friends, whose implementation
(not prototype!) includes use of volatile.
Regards,
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
