From: "Paul E. McKenney" <paulmck@kernel.org>
To: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
kernel-team@fb.com, mingo@kernel.org
Cc: stern@rowland.harvard.edu, parri.andrea@gmail.com,
will@kernel.org, peterz@infradead.org, boqun.feng@gmail.com,
npiggin@gmail.com, dhowells@redhat.com, j.alglave@ucl.ac.uk,
luc.maranget@inria.fr, akiyks@gmail.com,
SeongJae Park <sj@kernel.org>,
"Paul E . McKenney" <paulmck@kernel.org>
Subject: [PATCH memory-model 2/5] docs/memory-barriers.txt: Add a missed closing parenthesis
Date: Wed, 19 Oct 2022 16:06:48 -0700 [thread overview]
Message-ID: <20221019230651.2502538-2-paulmck@kernel.org> (raw)
In-Reply-To: <20221019230640.GA2502305@paulmck-ThinkPad-P17-Gen-1>
From: SeongJae Park <sj@kernel.org>
The description of io_stop_wc(), which was added by commit d5624bb29f49
("asm-generic: introduce io_stop_wc() and add implementation for ARM64"),
has an unclosed parenthesis. This commit closes it.
Fixes: d5624bb29f49 ("asm-generic: introduce io_stop_wc() and add implementation for ARM64")
Signed-off-by: SeongJae Park <sj@kernel.org>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
---
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 06f80e3785c5d..cc621decd9439 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -1966,7 +1966,7 @@ There are some more advanced barrier functions:
(*) io_stop_wc();
For memory accesses with write-combining attributes (e.g. those returned
- by ioremap_wc(), the CPU may wait for prior accesses to be merged with
+ by ioremap_wc()), the CPU may wait for prior accesses to be merged with
subsequent ones. io_stop_wc() can be used to prevent the merging of
write-combining memory accesses before this macro with those after it when
such wait has performance implications.
--
2.31.1.189.g2e36527f23
next prev parent reply other threads:[~2022-10-19 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 23:06 [PATCH memory-model 0/5] LKMM updates for v6.2 Paul E. McKenney
2022-10-19 23:06 ` [PATCH memory-model 1/5] tools/memory-model: Weaken ctrl dependency definition in explanation.txt Paul E. McKenney
2022-10-19 23:06 ` Paul E. McKenney [this message]
2022-10-19 23:06 ` [PATCH memory-model 3/5] docs/memory-barriers.txt/kokr: introduce io_stop_wc() and add implementation for ARM64 Paul E. McKenney
2022-10-19 23:06 ` [PATCH memory-model 4/5] docs/memory-barriers.txt/kokr: Add memory barrier dma_mb() Paul E. McKenney
2022-10-19 23:06 ` [PATCH memory-model 5/5] docs/memory-barriers.txt/kokr: Fix confusing name of 'data dependency barrier' Paul E. McKenney
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=20221019230651.2502538-2-paulmck@kernel.org \
--to=paulmck@kernel.org \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=j.alglave@ucl.ac.uk \
--cc=kernel-team@fb.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=mingo@kernel.org \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=peterz@infradead.org \
--cc=sj@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®