From 90abf8d955c4e43b1e9bbaa1e5220039e9cc0e59 Mon Sep 17 00:00:00 2001 From: Nikanth Karthikesan Date: Thu, 26 May 2011 16:25:13 -0700 Subject: [PATCH] --- yaml --- r: 252023 b: refs/heads/master c: 72eef0f3af410de2c85f236140ddea61b71cfc3e h: refs/heads/master i: 252021: 6f793b368b987f8347eb7429f5a129ed98406399 252019: 9b1e70771c4d3b25a47eabf0ab912ff73887108b 252015: d53329326e529b0f7909f3951575b25148518047 v: v3 --- [refs] | 2 +- trunk/Documentation/atomic_ops.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index 6d155969068d..94610ccb4936 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 1d5827235de48e829d5d4a03c3688ef6f2b15562 +refs/heads/master: 72eef0f3af410de2c85f236140ddea61b71cfc3e diff --git a/trunk/Documentation/atomic_ops.txt b/trunk/Documentation/atomic_ops.txt index ac4d47187122..3bd585b44927 100644 --- a/trunk/Documentation/atomic_ops.txt +++ b/trunk/Documentation/atomic_ops.txt @@ -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.