From: "Paul E. McKenney" <paulmck@kernel.org>
To: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
kernel-team@meta.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,
Kushagra Verma <kushagra765@outlook.com>,
"Paul E . McKenney" <paulmck@kernel.org>
Subject: [PATCH memory-model 3/4] Documentation: Fixed a typo in atomic_t.txt
Date: Wed, 4 Jan 2023 17:09:51 -0800 [thread overview]
Message-ID: <20230105010952.1774272-3-paulmck@kernel.org> (raw)
In-Reply-To: <20230105010944.GA1774169@paulmck-ThinkPad-P17-Gen-1>
From: Kushagra Verma <kushagra765@outlook.com>
Fixed a typo in the word 'architecture'.
Signed-off-by: Kushagra Verma <kushagra765@outlook.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
---
Documentation/atomic_t.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/atomic_t.txt b/Documentation/atomic_t.txt
index 0f1ffa03db09a..d7adc6d543db4 100644
--- a/Documentation/atomic_t.txt
+++ b/Documentation/atomic_t.txt
@@ -324,7 +324,7 @@ atomic operations.
Specifically 'simple' cmpxchg() loops are expected to not starve one another
indefinitely. However, this is not evident on LL/SC architectures, because
-while an LL/SC architecure 'can/should/must' provide forward progress
+while an LL/SC architecture 'can/should/must' provide forward progress
guarantees between competing LL/SC sections, such a guarantee does not
transfer to cmpxchg() implemented using LL/SC. Consider:
--
2.31.1.189.g2e36527f23
next prev parent reply other threads:[~2023-01-05 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 1:09 [PATCH memory-model 0/4] LKMM updates for v6.3 Paul E. McKenney
2023-01-05 1:09 ` [PATCH memory-model 1/4] locking/memory-barriers.txt: Improve documentation for writel() example Paul E. McKenney
2023-01-05 1:09 ` [PATCH memory-model 2/4] tools: memory-model: Add rmw-sequences to the LKMM Paul E. McKenney
2023-01-05 1:09 ` Paul E. McKenney [this message]
2023-01-05 1:09 ` [PATCH memory-model 4/4] tools: memory-model: Make plain accesses carry dependencies 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=20230105010952.1774272-3-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@meta.com \
--cc=kushagra765@outlook.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=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;
as well as URLs for NNTP newsgroup(s).