From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754337AbbBAVuL (ORCPT ); Sun, 1 Feb 2015 16:50:11 -0500 Received: from mail-wg0-f54.google.com ([74.125.82.54]:51092 "EHLO mail-wg0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753635AbbBAVuI (ORCPT ); Sun, 1 Feb 2015 16:50:08 -0500 From: Sharon Dvir To: peterz@infradead.org Cc: mingo@redhat.com, linux-kernel@vger.kernel.org, sharon.dvir1@mail.huji.ac.il Subject: [PATCH] Documentation: remove unneeded word. Date: Sun, 1 Feb 2015 23:47:32 +0200 Message-Id: <1422827252-31363-1-git-send-email-sharon.dvir1@mail.huji.ac.il> X-Mailer: git-send-email 2.1.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 --- 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.