From: Joe Perches <joe@perches.com>
To: Florian Vaussard <florian.vaussard@epfl.ch>
Cc: Andy Whitcroft <apw@canonical.com>, Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] checkpatch: fix spurious vendor compatible warnings
Date: Fri, 28 Feb 2014 13:06:11 -0800 [thread overview]
Message-ID: <1393621571.10280.49.camel@joe-AO722> (raw)
In-Reply-To: <1393604742-14317-3-git-send-email-florian.vaussard@epfl.ch>
Hi.
A couple of suggestions and a couple of questions.
I made the patch below against your patches to.
o Look for ".compatible = "foo" strings in .c and .h files too
o Improve the vendor name match in vendor-prefix.txt by only
matching the exact vendor name at the beginning of lines.
I then produced a file of all the compatible uses in dts
and used checkpatch on it. It's a long list and a longer
checkpatch warning list.
$ git ls-files | grep -E "\.dtsi?$" | \
xargs grep -hE "^\s*compatible\s*="| \
sed -r -e 's/^\s*//' -e 's/\s*=\s*/ = /'| sort | uniq > tmp.dts
$ .scripts/checkpatch.pl -f tmp.dts
A couple of questions:
How does the $compat2 variable actually work?
What is it supposed to do?
my $compat2 = $compat;
$compat2 =~ s/\,[a-z]*\-/\,<\.\*>\-/;
For instance:
WARNING: DT compatible string "marvell,tauros2-cache" appears un-documented -- check ./Documentation/devicetree/bindings/
The prefix "tauros2-" doesn't match '=~ s/[a-z]*-/
Should it? Should the '[a-z]*' be '[a-zA-Z0-9-]+'
like the other test?
Also the grep used when $compat2 is different than $compat
has <.*>
There aren't any descriptions I see in binding/ that have
any <foo> like uses with the angle brackets.
Are the angle brackets "<" and ">" necessary?
I think the code block should look more like:
my $compat2 = $compat;
$compat2 =~ s/\,[a-zA-Z0-9]*\-/\,\.\*\-/g;
my $grepfor = "\Q$compat\E";
$grepfor .= "|\Q$compat2\E" if ($compat2 ne $compat);
`grep -Erq "$grepfor" $dt_path`;
so that there's only 1 grep pattern when
$compat2 is the same as $compat and the
strings are escape quoted.
There are a _lot_ of missing entries:
o 164 vendor names
o 2408 device names (maybe due to bad compat2 greps?)
What, if anything, should be done about them?
---
scripts/checkpatch.pl | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 4b5e7b3..7a9eed9 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -2051,29 +2051,29 @@ sub process {
}
# check for DT compatible documentation
- if (defined $root && $realfile =~ /\.dts/ &&
- $rawline =~ /^\+\s*compatible\s*=/) {
+ if (defined $root &&
+ (($realfile =~ /\.dtsi?$/ && $line =~ /^\+\s*compatible\s*=\s*\"/) ||
+ ($realfile =~ /\.[ch]$/ && $line =~ /^\+.*\.compatible\s*=\s*\"/))) {
+
my @compats = $rawline =~ /\"([a-zA-Z0-9\-\,\.\+_]+)\"/g;
+ my $dt_path = $root . "/Documentation/devicetree/bindings/";
+ my $vp_file = $root . "/Documentation/devicetree/bindings/vendor-prefixes.txt";
+
foreach my $compat (@compats) {
my $compat2 = $compat;
- my $dt_path = $root . "/Documentation/devicetree/bindings/";
$compat2 =~ s/\,[a-z]*\-/\,<\.\*>\-/;
`grep -Erq "$compat|$compat2" $dt_path`;
if ( $? >> 8 ) {
WARN("UNDOCUMENTED_DT_STRING",
"DT compatible string \"$compat\" appears un-documented -- check $dt_path\n" . $herecurr);
}
-
- my $vendor = $compat;
- my $vendor_path = $dt_path . "vendor-prefixes.txt";
- next if (! -f $vendor_path);
- next if not $vendor =~ /^[a-zA-Z0-9\-]+\,.*/;
- $vendor =~ s/^([a-zA-Z0-9\-]+)\,.*/$1/;
- `grep -Eq "$vendor" $vendor_path`;
+ next if $compat !~ /^([a-zA-Z0-9\-]+)\,/;
+ my $vendor = $1;
+ `grep -Eq "^$vendor\\b" $vp_file`;
if ( $? >> 8 ) {
WARN("UNDOCUMENTED_DT_STRING",
- "DT compatible string vendor \"$vendor\" appears un-documented -- check $vendor_path\n" . $herecurr);
+ "DT compatible string vendor \"$vendor\" appears un-documented -- check $vp_file\n" . $herecurr);
}
}
}
---
next prev parent reply other threads:[~2014-02-28 21:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 16:25 [PATCH v2 0/2] checkpatch: fixes for vendor compatible check Florian Vaussard
2014-02-28 16:25 ` [PATCH v2 1/2] checkpatch: check vendor compatible with dashes Florian Vaussard
[not found] ` <1393604742-14317-1-git-send-email-florian.vaussard-p8DiymsW2f8@public.gmane.org>
2014-02-28 16:25 ` [PATCH v2 2/2] checkpatch: fix spurious vendor compatible warnings Florian Vaussard
2014-02-28 21:06 ` Joe Perches [this message]
2014-03-03 10:44 ` Florian Vaussard
[not found] ` <53145D21.4080101-p8DiymsW2f8@public.gmane.org>
2014-03-03 17:51 ` Joe Perches
2014-03-05 13:58 ` Florian Vaussard
2014-03-03 13:50 ` Rob Herring
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=1393621571.10280.49.camel@joe-AO722 \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=devicetree@vger.kernel.org \
--cc=florian.vaussard@epfl.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).