From: Joe Perches <joe@perches.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Andy Whitcroft <apw@canonical.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 2/2] checkpatch: Don't check for mutex_trylock_recursive()
Date: Wed, 10 Feb 2021 04:40:37 -0800 [thread overview]
Message-ID: <c2ca4fc47e61a597261509d16510db6c592d1c80.camel@perches.com> (raw)
In-Reply-To: <20210210085248.219210-3-bigeasy@linutronix.de>
On Wed, 2021-02-10 at 09:52 +0100, Sebastian Andrzej Siewior wrote:
> mutex_trylock_recursive() has been removed from the tree, there is no
> need to check for it.
>
> Remove traces of mutex_trylock_recursive()'s existence.
Yay. Assuming patch 1 is applied, thanks.
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> scripts/checkpatch.pl | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 1afe3af1cc097..4b2775fd31d9d 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -7062,12 +7062,6 @@ sub process {
> }
> }
>
>
> -# check for mutex_trylock_recursive usage
> - if ($line =~ /mutex_trylock_recursive/) {
> - ERROR("LOCKING",
> - "recursive locking is bad, do not use this ever.\n" . $herecurr);
> - }
> -
> # check for lockdep_set_novalidate_class
> if ($line =~ /^.\s*lockdep_set_novalidate_class\s*\(/ ||
> $line =~ /__lockdep_no_validate__\s*\)/ ) {
next prev parent reply other threads:[~2021-02-10 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 8:52 [PATCH 0/2] locking/mutex: Kill mutex_trylock_recursive() Sebastian Andrzej Siewior
2021-02-10 8:52 ` [PATCH 1/2] " Sebastian Andrzej Siewior
2021-02-10 13:59 ` [tip: locking/core] " tip-bot2 for Sebastian Andrzej Siewior
2021-02-10 8:52 ` [PATCH 2/2] checkpatch: Don't check for mutex_trylock_recursive() Sebastian Andrzej Siewior
2021-02-10 12:40 ` Joe Perches [this message]
2021-02-10 13:59 ` [tip: locking/core] " tip-bot2 for Sebastian Andrzej Siewior
2021-02-10 9:17 ` [PATCH 0/2] locking/mutex: Kill mutex_trylock_recursive() Peter Zijlstra
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=c2ca4fc47e61a597261509d16510db6c592d1c80.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.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
all inboxes | Powered by JetHome®