The patch titled
typo fixes for rt-mutex-design.txt
has been removed from the -mm tree. Its filename is
typo-fixes-for-rt-mutex-designtxt.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: typo fixes for rt-mutex-design.txt
From: Jan Altenberg <tb10alj@xxxxxxx>
Address some simple typos in rt-mutex-design.txt It also changes the
indentation of the cmpxchg example (the cmpxchg example was indented by
spaces, while all other code snippets were indented by tabs).
Acked-by: Steven Rostedt <rostedt@xxxxxxxxxxx>
Signed-off-by: Jan Altenberg <tb10alj@xxxxxxx>
Acked-by: Ingo Molnar <mingo@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
Documentation/rt-mutex-design.txt | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff -puN Documentation/rt-mutex-design.txt~typo-fixes-for-rt-mutex-designtxt Documentation/rt-mutex-design.txt
--- a/Documentation/rt-mutex-design.txt~typo-fixes-for-rt-mutex-designtxt
+++ a/Documentation/rt-mutex-design.txt
@@ -333,11 +333,11 @@ cmpxchg is basically the following funct
unsigned long _cmpxchg(unsigned long *A, unsigned long *B, unsigned long *C)
{
- unsigned long T = *A;
- if (*A == *B) {
- *A = *C;
- }
- return T;
+ unsigned long T = *A;
+ if (*A == *B) {
+ *A = *C;
+ }
+ return T;
}
#define cmpxchg(a,b,c) _cmpxchg(&a,&b,&c)
@@ -582,7 +582,7 @@ contention).
try_to_take_rt_mutex is used every time the task tries to grab a mutex in the
slow path. The first thing that is done here is an atomic setting of
the "Has Waiters" flag of the mutex's owner field. Yes, this could really
-be false, because if the the mutex has no owner, there are no waiters and
+be false, because if the mutex has no owner, there are no waiters and
the current task also won't have any waiters. But we don't have the lock
yet, so we assume we are going to be a waiter. The reason for this is to
play nice for those architectures that do have CMPXCHG. By setting this flag
@@ -735,7 +735,7 @@ do have CMPXCHG, that check is done in t
in the slow path too. If a waiter of a mutex woke up because of a signal
or timeout between the time the owner failed the fast path CMPXCHG check and
the grabbing of the wait_lock, the mutex may not have any waiters, thus the
-owner still needs to make this check. If there are no waiters than the mutex
+owner still needs to make this check. If there are no waiters then the mutex
owner field is set to NULL, the wait_lock is released and nothing more is
needed.
_
Patches currently in -mm which might be from tb10alj@xxxxxxx are
origin.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
