From: Brian Norris <computersforpeace@gmail.com>
To: Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
SF Markus Elfring <elfring@users.sourceforge.net>
Subject: Re: [PATCH] checkpatch: fix uninitialized var when run with --no-tree
Date: Fri, 28 Oct 2016 19:36:09 -0700 [thread overview]
Message-ID: <20161029023609.GA48401@google.com> (raw)
In-Reply-To: <1477707991-140274-1-git-send-email-briannorris@chromium.org>
On Fri, Oct 28, 2016 at 07:26:31PM -0700, Brian Norris wrote:
> From: Brian Norris <computersforpeace@gmail.com>
>
> If checkpatch.pl gets copied out of the tree, --no-tree shouldn't start
> complaining:
>
> Use of uninitialized value $root in concatenation (.) or string at
> /path/to/checkpatch.pl line 764.
>
> Let's just give the safe answer instead -- don't warn about "obsolete"
> files.
>
> Fixes: 85b0ee18bbf8 ("checkpatch: see if modified files are marked obsolete in MAINTAINERS")
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
> ---
> This is a 4.9-rc1 regression
>
> scripts/checkpatch.pl | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index a8368d1c4348..c8cd643dbc6f 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -761,6 +761,8 @@ sub seed_camelcase_file {
> sub is_maintained_obsolete {
> my ($filename) = @_;
>
> + return 0 if (!$tree);
Actually, I'm torn on this. It looks really odd to check for !$tree
here, but it's the only supported case where $root shouldn't be defined.
Maybe (!defined $root) is a better test? (Sorry, I did a double-take on
this after I sent it.)
Both would be equally correct, but I suppose the latter would be
clearer. I'll send v2.
Brian
> +
> return 0 if (!(-e "$root/scripts/get_maintainer.pl"));
>
> my $status = `perl $root/scripts/get_maintainer.pl --status --nom --nol --nogit --nogit-fallback -f $filename 2>&1`;
> --
> 2.8.0.rc3.226.g39d4020
>
next prev parent reply other threads:[~2016-10-29 2:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 2:26 Brian Norris
2016-10-29 2:36 ` Brian Norris [this message]
2016-11-08 23:10 ` Andrew Morton
2016-11-09 0:00 ` Brian Norris
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=20161029023609.GA48401@google.com \
--to=computersforpeace@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=elfring@users.sourceforge.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome