rt-mutex.txt has been moved to Documentation/locking by 214e0aed639ef40987bf6159fad303171a6de31e in 3.18-rc1, so modify the reference in Documentation/locking/rt-mutex-design.txt.
---------------------------------------- Signed-off-by: Zhiqiang Zhang <[email protected]> --- Documentation/locking/rt-mutex-design.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/locking/rt-mutex-design.txt b/Documentation/locking/rt-mutex-design.txt index 8666070..8c72ccd 100644 --- a/Documentation/locking/rt-mutex-design.txt +++ b/Documentation/locking/rt-mutex-design.txt @@ -8,7 +8,7 @@ RT-mutex implementation design This document tries to describe the design of the rtmutex.c implementation. It doesn't describe the reasons why rtmutex.c exists. For that please see -Documentation/rt-mutex.txt. Although this document does explain problems +Documentation/locking/rt-mutex.txt. Although this document does explain problems that happen without this code, but that is in the concept to understand what the code actually is doing. @@ -315,7 +315,7 @@ mutex is not owned, this owner is set to NULL. Since all architectures have the task structure on at least a four byte alignment (and if this is not true, the rtmutex.c code will be broken!), this allows for the two least significant bits to be used as flags. This part is also described -in Documentation/rt-mutex.txt, but will also be briefly described here. +in Documentation/locking/rt-mutex.txt, but will also be briefly described here. Bit 0 is used as the "Pending Owner" flag. This is described later. Bit 1 is used as the "Has Waiters" flags. This is also described later -- 1.9.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
