The patch titled
mutex: improve header comment to be actually informative about the API
has been added to the -mm tree. Its filename is
mutex-improve-header-comment-to-be-actually-informative-about-the-api.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: mutex: improve header comment to be actually informative about the API
From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
It's nice to say that mutex_trylock follows the spin_trylock convention.
It's a lot nicer if the comment also says which that is... make it so.
Signed-off-by: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
Cc: Ingo Molnar <mingo@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/linux/mutex.h | 2 ++
1 file changed, 2 insertions(+)
diff -puN include/linux/mutex.h~mutex-improve-header-comment-to-be-actually-informative-about-the-api include/linux/mutex.h
--- a/include/linux/mutex.h~mutex-improve-header-comment-to-be-actually-informative-about-the-api
+++ a/include/linux/mutex.h
@@ -144,6 +144,8 @@ extern int __must_check mutex_lock_killa
/*
* NOTE: mutex_trylock() follows the spin_trylock() convention,
* not the down_trylock() convention!
+ *
+ * Returns 1 if the mutex has been acquired successfully, and 0 on contention.
*/
extern int mutex_trylock(struct mutex *lock);
extern void mutex_unlock(struct mutex *lock);
_
Patches currently in -mm which might be from arjan@xxxxxxxxxxxxxxx are
git-x86.patch
git-net.patch
git-fastboot.patch
mutex-improve-header-comment-to-be-actually-informative-about-the-api.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
