From: Joe Perches <joe@perches.com>
To: Jeremy Sowden <jeremy@azazel.net>,
linux-kernel@vger.kernel.org, apw@canonical.com
Subject: Re: [PATCH] checkpatch: fix for stripping brackets from macros.
Date: Mon, 18 Dec 2017 07:12:50 -0800 [thread overview]
Message-ID: <1513609970.31581.62.camel@perches.com> (raw)
In-Reply-To: <20171218141716.26227-1-jeremy@azazel.net>
On Mon, 2017-12-18 at 14:17 +0000, Jeremy Sowden wrote:
> When checking macros, checkpatch.pl strips parentheses, square brackets
> and braces. However, the search-and-replace expression was not correct,
> and instead of replacing the brackets and their contents with just the
> contents, it was replacing them with literal 1's.
Jeremy:
What is the effect on the rest of the block that
uses this substituted
$dstat? Why should this be
done?
Andy:
I believe this is intentional as it simplifies
the macro analysis and has no other effect on the
rest of the block. Correct?
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -4874,9 +4874,9 @@ sub process {
> $dstat =~ s/\s*$//s;
>
> # Flatten any parentheses and braces
> - while ($dstat =~ s/\([^\(\)]*\)/1/ ||
> - $dstat =~ s/\{[^\{\}]*\}/1/ ||
> - $dstat =~ s/.\[[^\[\]]*\]/1/)
> + while ($dstat =~ s/\(([^\(\)]*)\)/$1/ ||
> + $dstat =~ s/\{([^\{\}]*)\}/$1/ ||
> + $dstat =~ s/.\[([^\[\]]*)\]/$1/)
> {
> }
next prev parent reply other threads:[~2017-12-18 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 14:17 Jeremy Sowden
2017-12-18 15:12 ` Joe Perches [this message]
2017-12-18 16:23 ` Jeremy Sowden
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=1513609970.31581.62.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=jeremy@azazel.net \
--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
Powered by JetHome