From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: Re: [PATCH v7 02/17] locks: clean up comment typo Date: Sun, 23 Mar 2014 15:54:45 -0400 Message-ID: <20140323195445.GA6103@fieldses.org> References: <1395261961-10855-1-git-send-email-jlayton@redhat.com> <1395261961-10855-3-git-send-email-jlayton@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: viro@ZenIV.linux.org.uk, linux-fsdevel@vger.kernel.org To: Jeff Layton Return-path: Received: from fieldses.org ([174.143.236.118]:47105 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750914AbaCWTys (ORCPT ); Sun, 23 Mar 2014 15:54:48 -0400 Content-Disposition: inline In-Reply-To: <1395261961-10855-3-git-send-email-jlayton@redhat.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, Mar 19, 2014 at 04:45:46PM -0400, Jeff Layton wrote: > Signed-off-by: Jeff Layton Acked-by: J. Bruce Fields > --- > fs/locks.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/fs/locks.c b/fs/locks.c > index 2cfeea622f28..5e28612120c2 100644 > --- a/fs/locks.c > +++ b/fs/locks.c > @@ -581,7 +581,7 @@ static void locks_delete_block(struct file_lock *waiter) > * it seems like the reasonable thing to do. > * > * Must be called with both the i_lock and blocked_lock_lock held. The fl_block > - * list itself is protected by the file_lock_list, but by ensuring that the > + * list itself is protected by the blocked_lock_lock, but by ensuring that the > * i_lock is also held on insertions we can avoid taking the blocked_lock_lock > * in some cases when we see that the fl_block list is empty. > */ > -- > 1.8.5.3 >