diff options
| author | Kushagra Verma <kushagra765@outlook.com> | 2022-11-29 18:50:59 +0530 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@kernel.org> | 2023-01-03 20:47:04 -0800 |
| commit | aae0c8a50d6d312d87188cf4dc8bde8c253978d7 (patch) | |
| tree | d99d4c9b709a98b632393b704a732afaee59f0b6 /Documentation/atomic_t.txt | |
| parent | ebd50e2947de9d2675b800a6a29748d0ed7d7fd4 (diff) | |
Documentation: Fixed a typo in atomic_t.txt
Fixed a typo in the word 'architecture'.
Signed-off-by: Kushagra Verma <kushagra765@outlook.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'Documentation/atomic_t.txt')
| -rw-r--r-- | Documentation/atomic_t.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/atomic_t.txt b/Documentation/atomic_t.txt index 0f1ffa03db09..d7adc6d543db 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: |