LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* [PATCH] Documentation: remove unneeded word.
@ 2015-02-01 21:47 Sharon Dvir
  2015-02-04 14:37 ` [tip:sched/core] sched/Documentation: Remove " tip-bot for Sharon Dvir
  0 siblings, 1 reply; 2+ messages in thread
From: Sharon Dvir @ 2015-02-01 21:47 UTC (permalink / raw)
  To: peterz; +Cc: mingo, linux-kernel, sharon.dvir1

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 <sharon.dvir1@mail.huji.ac.il>
---
diff --git a/kernel/locking/mutex.c b/kernel/locking/mutex.c
index c67a60b..ac07973 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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [tip:sched/core] sched/Documentation: Remove unneeded word
  2015-02-01 21:47 [PATCH] Documentation: remove unneeded word Sharon Dvir
@ 2015-02-04 14:37 ` tip-bot for Sharon Dvir
  0 siblings, 0 replies; 2+ messages in thread
From: tip-bot for Sharon Dvir @ 2015-02-04 14:37 UTC (permalink / raw)
  To: linux-tip-commits
  Cc: mingo, linux-kernel, torvalds, hpa, peterz, sharon.dvir1, tglx

Commit-ID:  139b6fd26d85a65c4e0d2795b87b94f9505e5943
Gitweb:     http://git.kernel.org/tip/139b6fd26d85a65c4e0d2795b87b94f9505e5943
Author:     Sharon Dvir <sharon.dvir1@mail.huji.ac.il>
AuthorDate: Sun, 1 Feb 2015 23:47:32 +0200
Committer:  Ingo Molnar <mingo@kernel.org>
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 <sharon.dvir1@mail.huji.ac.il>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Link: http://lkml.kernel.org/r/1422827252-31363-1-git-send-email-sharon.dvir1@mail.huji.ac.il
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
 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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-02-04 14:37 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-01 21:47 [PATCH] Documentation: remove unneeded word Sharon Dvir
2015-02-04 14:37 ` [tip:sched/core] sched/Documentation: Remove " tip-bot for Sharon Dvir

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).