Documentation/atomic_ops.txt: avoid volatile in sample code
Subsystems (2)
PATCH 1/1 Documentation/atomic_ops.txt: avoid volatile in sample code
As declaring counter as volatile is discouraged, it is best not to use it in sample code as well.
Signed-off-by Nikanth Karthikesan <[email protected]>
---
Documentation/atomic_ops.txt +1 -1
@@ -12,7 +12,7 @@ Also, it should be made opaque such that any kind of cast to a normal C integer type will fail. Something like the following should suffice: - typedef struct { volatile int counter; } atomic_t; + typedef struct { int counter; } atomic_t; Historically, counter has been declared volatile. This is now discouraged. See Documentation/volatile-considered-harmful.txt for the complete rationale.