From: Pekka Enberg <penberg@iki.fi>
To: Peter Zijlstra <peterz@infradead.org>, penberg@kernel.org
Cc: Christoph Lameter <cl@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mpm@selenic.com
Subject: Re: [PATCH] slub: use lockdep_assert_held
Date: Mon, 13 Jan 2014 21:34:51 +0200 [thread overview]
Message-ID: <52D43FDB.9090003@iki.fi> (raw)
In-Reply-To: <20140110122349.GN31570@twins.programming.kicks-ass.net>
On 01/10/2014 02:23 PM, Peter Zijlstra wrote:
> Instead of using comments in an attempt at getting the locking right,
> use proper assertions that actively warn you if you got it wrong.
>
> Also add extra braces in a few sites to comply with coding-style.
>
> Signed-off-by: Peter Zijlstra <peterz@infradead.org>
>
Applied, thanks!
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2014-01-14 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 12:23 Peter Zijlstra
2014-01-13 19:34 ` Pekka Enberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52D43FDB.9090003@iki.fi \
--to=penberg@iki.fi \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox