From: Joe Perches <joe@perches.com>
To: Andy Whitcroft <apw@canonical.com>
Cc: Rob Herring <robherring2@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <rob.herring@calxeda.com>,
Grant Likely <grant.likely@linaro.org>
Subject: Re: [PATCH v3] checkpatch: add DT compatible string documentation checks
Date: Fri, 06 Dec 2013 08:48:30 -0800 [thread overview]
Message-ID: <1386348510.31845.30.camel@joe-AO722> (raw)
In-Reply-To: <20131206095626.GD3248@bark>
On Fri, 2013-12-06 at 09:56 +0000, Andy Whitcroft wrote:
> On Wed, Dec 04, 2013 at 08:12:43AM -0800, Joe Perches wrote:
> > On Wed, 2013-12-04 at 10:03 -0600, Rob Herring wrote:
> > > From: Rob Herring <rob.herring@calxeda.com>
> > >
> > > This adds a simple check that any compatible strings in DeviceTree dts
> > > files are present in Documentation/devicetree/bindings. Vendor prefixes
> > > are also checked for existing in vendor-prefixes.txt These should be
> > > temporary checks until we have more sophisticated binding schema checking.
[]
> > > +# check for DT compatible documentation
> > > + if ($realfile =~ /\.dts/ && $rawline =~ /^\+\s*compatible\s*=/) {
> > > + my @compats = $rawline =~ /\"([a-zA-Z0-9\-\,\.\+_]+)\"/g;
> > > +
> > > + foreach my $compat (@compats) {
> > > + my $compat2 = $compat;
> > > + my $dt_path = "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";
> > > + $vendor =~ s/^([a-zA-Z0-9]+)\,.*/$1/;
> > > + `grep -Eq "$vendor" $vendor_path`;
> > > + if ( $? >> 8 ) {
> > > + WARN("UNDOCUMENTED_DT_STRING",
> > > + "DT compatible string vendor \"$vendor\" appears un-documented -- check $vendor_path\n" . $herecurr);
> > > + }
> > > + }
> > > + }
>
> So this only works if you are in the top of the tree at the time when
> you run it (unless I've missed something). So it might be appropraite
> to suppress this when the vendor-prefixes.txt file is not found.
I suppose it's useful to use the $root variable
on the file open too.
my $vendor_path = $root . '/' . $dt_path . "vendor-prefixes.txt";
prev parent reply other threads:[~2013-12-06 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 16:03 Rob Herring
2013-12-04 16:12 ` Joe Perches
2013-12-06 9:56 ` Andy Whitcroft
2013-12-06 16:48 ` 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=1386348510.31845.30.camel@joe-AO722 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=robherring2@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
all inboxes | Powered by JetHome®