LKML Archive on
help / color / mirror / Atom feed
From: tip-bot for Sharon Dvir <>
Subject: [tip:sched/core] sched/Documentation: Remove unneeded word
Date: Wed, 4 Feb 2015 06:37:06 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Commit-ID:  139b6fd26d85a65c4e0d2795b87b94f9505e5943
Author:     Sharon Dvir <>
AuthorDate: Sun, 1 Feb 2015 23:47:32 +0200
Committer:  Ingo Molnar <>
CommitDate: Wed, 4 Feb 2015 07:52:33 +0100

sched/Documentation: Remove unneeded word

The second 'mutex' shouldn't be there, it can't be about the mutex,
as the mutex can't be freed, but unlocked, the memory where the
mutex resides however, can be freed.

Signed-off-by: Sharon Dvir <>
Signed-off-by: Peter Zijlstra (Intel) <>
Cc: Linus Torvalds <>
Signed-off-by: Ingo Molnar <>
 kernel/locking/mutex.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/locking/mutex.c b/kernel/locking/mutex.c
index 4541951..5b49f65 100644
--- a/kernel/locking/mutex.c
+++ b/kernel/locking/mutex.c
@@ -81,7 +81,7 @@ __visible void __sched __mutex_lock_slowpath(atomic_t *lock_count);
  * The mutex must later on be released by the same task that
  * acquired it. Recursive locking is not allowed. The task
  * may not exit without first unlocking the mutex. Also, kernel
- * memory where the mutex resides mutex must not be freed with
+ * memory where the mutex resides must not be freed with
  * the mutex still locked. The mutex must first be initialized
  * (or statically defined) before it can be locked. memset()-ing
  * the mutex to 0 is not allowed.

      reply	other threads:[~2015-02-04 14:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-01 21:47 [PATCH] Documentation: remove " Sharon Dvir
2015-02-04 14:37 ` tip-bot for Sharon Dvir [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [tip:sched/core] sched/Documentation: Remove unneeded word' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).