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

[Peter Zijlstra]

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/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/