From: Joe Perches <joe@perches.com>
To: Constantine Shulyupin <const@MakeLinux.com>
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
Andy Whitcroft <apw@canonical.com>
Subject: Re: [PATCH] checkpatch: debugfs_remove() can take NULL
Date: Sat, 17 Nov 2012 05:30:17 -0800 [thread overview]
Message-ID: <1353159017.12430.21.camel@joe-AO722> (raw)
In-Reply-To: <1353155581-30852-1-git-send-email-const@MakeLinux.com>
On Sat, 2012-11-17 at 14:33 +0200, Constantine Shulyupin wrote:
> From: Constantine Shulyupin <const@MakeLinux.com>
>
> debugfs_remove() can take a NULL, so let's check and warn about that.
>
> Signed-off-by: Constantine Shulyupin <const@MakeLinux.com>
> ---
> scripts/checkpatch.pl | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index f18750e..c062476 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -3221,6 +3221,14 @@ sub process {
> "kfree(NULL) is safe this check is probably not required\n" . $hereprev);
> }
> }
> +# check for needless debugfs_remove() checks
> + if ($prevline =~ /\bif\s*\(([^\)]*)\)/) {
> + my $expr = $1;
> + if ($line =~ /\bdebugfs_remove\(\Q$expr\E\);/) {
> + WARN("NEEDLESS_DEBUGFS_REMOVE",
> + "debugfs_remove(NULL) is safe this check is probably not required\n" . $hereprev);
> + }
> + }
> # check for needless usb_free_urb() checks
> if ($prevline =~ /\bif\s*\(([^\)]*)\)/) {
> my $expr = $1;
Perhaps debugfs_remove_recursive should be added too.
Please create a consolidated block of tests for these
checks of:
if (foo)
something_with(foo)
and add kfree, usb_free_urb and your debugfs_remove (and
debugfs_remove_recursive?) to that block so that the
"if ($prevline..." test is done only once per patch line.
prev parent reply other threads:[~2012-11-17 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 12:33 Constantine Shulyupin
2012-11-17 13:30 ` Joe Perches [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=1353159017.12430.21.camel@joe-AO722 \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=const@MakeLinux.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.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®