From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753794AbbJNN6t (ORCPT ); Wed, 14 Oct 2015 09:58:49 -0400 Received: from mail-wi0-f181.google.com ([209.85.212.181]:33487 "EHLO mail-wi0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753094AbbJNN6r (ORCPT ); Wed, 14 Oct 2015 09:58:47 -0400 Date: Wed, 14 Oct 2015 15:58:29 +0200 From: Ingo Molnar To: Peter Zijlstra Cc: Mark Brown , Arnd Bergmann , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Liam Girdwood , akpm@linux-foundation.org, Sascha Hauer Subject: Re: [PATCH] mutex: make mutex_lock_nested an inline function Message-ID: <20151014135829.GA10942@gmail.com> References: <11282238.AHmyWliPRj@wuerfel> <20151013203812.GM17308@twins.programming.kicks-ass.net> <11817958.z9KtmeKzV7@wuerfel> <20151014082050.GQ17308@twins.programming.kicks-ass.net> <20151014102706.GR14956@sirena.org.uk> <20151014110717.GT17308@twins.programming.kicks-ass.net> <20151014123624.GV14956@sirena.org.uk> <20151014134721.GD3816@twins.programming.kicks-ass.net> <20151014135005.GS11639@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151014135005.GS11639@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Peter Zijlstra wrote: > On Wed, Oct 14, 2015 at 03:47:21PM +0200, Peter Zijlstra wrote: > > --- > > Documentation/locking/lockdep-design.txt | 8 ++++++++ > > 1 file changed, 8 insertions(+) > > > > diff --git a/Documentation/locking/lockdep-design.txt b/Documentation/locking/lockdep-design.txt > > index 5001280e9d82..e8e9ad4e6f5e 100644 > > --- a/Documentation/locking/lockdep-design.txt > > +++ b/Documentation/locking/lockdep-design.txt > > @@ -24,6 +24,10 @@ a lock-class is used for the first time after bootup it gets registered, > > and all subsequent uses of that lock-class will be attached to this > > lock-class. > > > > +A class is typically associated with a lock's initialisation site; although > > +its possible to explicitly initialize a lock with a different class key -- > > +such class keys much come from static storage. > > Now if only I could actually type: s/much/must/ also: s/its/it's :-) Thanks, Ingo