From: SeongJae Park <sj38.park@gmail.com>
To: corbet@lwn.net, dhowells@redhat.com, paulmck@linux.vnet.ibm.com
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH] Documentation/memory-barriers: fix wrong comment in example
Date: Sat, 20 Feb 2016 15:01:08 +0900 [thread overview]
Message-ID: <1455948068-14221-1-git-send-email-sj38.park@gmail.com> (raw)
There is wrong comment in example for compiler store omit behavior. It
shows example of the problem and than problem solved version code.
However, the comment in the solved version is still same with not solved
version. Fix the wrong statement with this commit.
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
Documentation/memory-barriers.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index 061ff29..b4754c7 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -1471,7 +1471,7 @@ of optimizations:
wrong guess:
WRITE_ONCE(a, 0);
- /* Code that does not store to variable a. */
+ /* Code that does store to variable a. */
WRITE_ONCE(a, 0);
(*) The compiler is within its rights to reorder memory accesses unless
--
1.9.1
next reply other threads:[~2016-02-20 6:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 6:01 SeongJae Park [this message]
2016-02-20 19:57 ` [PATCH] Documentation/memory-barriers: fix wrong comment in example Paul E. McKenney
2016-02-20 22:50 ` SeongJae Park
2016-02-21 5:25 ` Paul E. McKenney
2016-02-21 6:33 ` SeongJae Park
2016-02-22 10:01 ` David Howells
2016-02-22 11:08 ` SeongJae Park
2016-02-22 11:16 ` David Howells
2016-02-22 16:33 ` Paul E. McKenney
2016-02-22 21:45 ` SeongJae Park
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1455948068-14221-1-git-send-email-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox