From 80fc01036fc88ccb364463ce879d2eebd0bee597 Mon Sep 17 00:00:00 2001 From: Jim Cromie Date: Thu, 3 Jun 2010 08:40:55 -0600 Subject: [PATCH] --- yaml --- r: 204405 b: refs/heads/master c: c20cbe46bd5c13444e30cefc997704514dc74cc5 h: refs/heads/master i: 204403: af1bbe882caa472884a8a47a2802793d19e1295c v: v3 --- [refs] | 2 +- trunk/Documentation/rt-mutex-design.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index eceeb68acfd5..950d15544c21 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 724df615928b7050d33b6243f60b12bd87484fc7 +refs/heads/master: c20cbe46bd5c13444e30cefc997704514dc74cc5 diff --git a/trunk/Documentation/rt-mutex-design.txt b/trunk/Documentation/rt-mutex-design.txt index 8df0b782c4d7..33ed8007a845 100644 --- a/trunk/Documentation/rt-mutex-design.txt +++ b/trunk/Documentation/rt-mutex-design.txt @@ -364,7 +364,7 @@ process this is rather easy to know what needs to be adjusted. The functions implementing the task adjustments are rt_mutex_adjust_prio, __rt_mutex_adjust_prio (same as the former, but expects the task pi_lock -to already be taken), rt_mutex_get_prio, and rt_mutex_setprio. +to already be taken), rt_mutex_getprio, and rt_mutex_setprio. rt_mutex_getprio and rt_mutex_setprio are only used in __rt_mutex_adjust_prio.