[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230105010952.1774272-3-paulmck@kernel.org>
Date: Wed, 4 Jan 2023 17:09:51 -0800
From: "Paul E. McKenney" <paulmck@...nel.org>
To: linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
kernel-team@...a.com, mingo@...nel.org
Cc: stern@...land.harvard.edu, parri.andrea@...il.com, will@...nel.org,
peterz@...radead.org, boqun.feng@...il.com, npiggin@...il.com,
dhowells@...hat.com, j.alglave@....ac.uk, luc.maranget@...ia.fr,
akiyks@...il.com, Kushagra Verma <kushagra765@...look.com>,
"Paul E . McKenney" <paulmck@...nel.org>
Subject: [PATCH memory-model 3/4] Documentation: Fixed a typo in atomic_t.txt
From: Kushagra Verma <kushagra765@...look.com>
Fixed a typo in the word 'architecture'.
Signed-off-by: Kushagra Verma <kushagra765@...look.com>
Signed-off-by: Paul E. McKenney <paulmck@...nel.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
Powered by blists - more mailing lists