Documentation/atomic_t.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Fixed a typo in the word 'architecture'.
Signed-off-by: Kushagra Verma <kushagra765@outlook.com>
---
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 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:
--
2.38.1
On Tue, Nov 29, 2022 at 06:50:59PM +0530, Kushagra Verma wrote: > Fixed a typo in the word 'architecture'. > > Signed-off-by: Kushagra Verma <kushagra765@outlook.com> Good eyes! Queued for further review, thank you! Thanx, Paul > --- > 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 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: > > -- > 2.38.1 >
© 2016 - 2025 Red Hat, Inc.