From: Peter Zijlstra <peterz@infradead.org>
To: Ming Lei <tom.leiming@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] lockdep: fix warning in case of no_validate lock
Date: Tue, 9 Aug 2016 14:53:14 +0200 [thread overview]
Message-ID: <20160809125314.GI30192@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1468379196-21096-1-git-send-email-tom.leiming@gmail.com>
On Wed, Jul 13, 2016 at 11:06:36AM +0800, Ming Lei wrote:
> Now there are several locks which are marked as
> no_validate, so name of the lock class can be
> different with the no_validate lock.
Hurgh, how did that happen? See checkpatch saying:
scripts/checkpatch.pl: "lockdep_no_validate class is reserved for device->mutex.\n" . $herecurr);
> This patch avoids this warning for this case, and
> fix the following warning:
I'm not sure we want that.. given we should strive for less no_validate
usage, not more.
prev parent reply other threads:[~2016-08-09 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 3:06 Ming Lei
2016-08-09 11:17 ` Ming Lei
2016-08-09 12:53 ` Peter Zijlstra [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=20160809125314.GI30192@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tom.leiming@gmail.com \
/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
Powered by JetHome