diff options
| author | Linus Torvalds <torvalds@woody.osdl.org> | 2006-12-06 14:42:57 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@woody.osdl.org> | 2006-12-06 14:42:57 -0800 |
| commit | f9e9dcb38f5106fa8cdac04a9e967d5487f1cd20 (patch) | |
| tree | 8d1cbf17b9b54eacde5a7bf7adf4d5ba6cb119dc /include/asm-x86_64 | |
| parent | 16afea0255cf6963eb924d4334cdb5acb9074581 (diff) | |
x86[-64]:Remove 'volatile' from atomic_t
Any code that relies on the volatile would be a bug waiting to happen
anyway.
Don't encourage people to think that putting 'volatile' on data
structures somehow fixes problems. We should always use proper locking
(and other serialization) techniques.
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'include/asm-x86_64')
| -rw-r--r-- | include/asm-x86_64/atomic.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/include/asm-x86_64/atomic.h b/include/asm-x86_64/atomic.h index 007e88d6d43..93849f7abc2 100644 --- a/include/asm-x86_64/atomic.h +++ b/include/asm-x86_64/atomic.h @@ -21,7 +21,7 @@ * on us. We need to use _exactly_ the address the user gave us, * not some alias that contains the same information. */ -typedef struct { volatile int counter; } atomic_t; +typedef struct { int counter; } atomic_t; #define ATOMIC_INIT(i) { (i) } |