From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755889AbbBDOhq (ORCPT ); Wed, 4 Feb 2015 09:37:46 -0500 Received: from terminus.zytor.com ([198.137.202.10]:38778 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755825AbbBDOhm (ORCPT ); Wed, 4 Feb 2015 09:37:42 -0500 Date: Wed, 4 Feb 2015 06:37:06 -0800 From: tip-bot for Sharon Dvir Message-ID: Cc: mingo@kernel.org, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, hpa@zytor.com, peterz@infradead.org, sharon.dvir1@mail.huji.ac.il, tglx@linutronix.de Reply-To: peterz@infradead.org, linux-kernel@vger.kernel.org, hpa@zytor.com, torvalds@linux-foundation.org, mingo@kernel.org, tglx@linutronix.de, sharon.dvir1@mail.huji.ac.il In-Reply-To: <1422827252-31363-1-git-send-email-sharon.dvir1@mail.huji.ac.il> References: <1422827252-31363-1-git-send-email-sharon.dvir1@mail.huji.ac.il> To: linux-tip-commits@vger.kernel.org Subject: [tip:sched/core] sched/Documentation: Remove unneeded word Git-Commit-ID: 139b6fd26d85a65c4e0d2795b87b94f9505e5943 X-Mailer: tip-git-log-daemon Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Commit-ID: 139b6fd26d85a65c4e0d2795b87b94f9505e5943 Gitweb: http://git.kernel.org/tip/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 Link: http://lkml.kernel.org/r/1422827252-31363-1-git-send-email-sharon.dvir1@mail.huji.ac.il 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.