Re: [PATCH] mutex: make mutex_lock_nested an inline function

From: Peter Zijlstra <peterz@infradead.org>
To: Mark Brown <broonie@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Liam Girdwood <lgirdwood@gmail.com>,
	akpm@linux-foundation.org, Sascha Hauer <kernel@pengutronix.de>
Subject: Re: [PATCH] mutex: make mutex_lock_nested an inline function
Date: Wed, 14 Oct 2015 15:50:05 +0200	[thread overview]
Message-ID: <20151014135005.GS11639@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20151014134721.GD3816@twins.programming.kicks-ass.net>

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/