From: Eric Blake <eblake@redhat.com>
To: Su Hang <suhang16@mails.ucas.ac.cn>, vsementsov@virtuozzo.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC] scripts/checkpatch.pl: Bug fix
Date: Mon, 19 Mar 2018 10:25:20 -0500 [thread overview]
Message-ID: <938b752e-770a-b8d2-d51f-55ef412973ae@redhat.com> (raw)
In-Reply-To: <1521467768-3162-1-git-send-email-suhang16@mails.ucas.ac.cn>
On 03/19/2018 08:56 AM, Su Hang wrote:
> Bug fix: checkpatch.pl stops complaining about following pattern:
> """
> do {
> //do somethins;
s/somethins/something/
> } while (conditions);
Having the commit message point to the commit id that introduced the bug
is useful. The grammar is awkward (it sounds like the bug is that
checkpatch.pl stopped complaining about the pattern, so the fix is to
reinstate the complaint); better might be:
Commit XYZ introduced a regression: checkpatch.pl started complaining
about the following valid pattern:
do {
/* something */
} while (condition);
Fix the script to once again permit this pattern.
> """
>
> Signed-off-by: Su Hang <suhang16@mails.ucas.ac.cn>
> ---
Is this an updated revision to a patch posted earlier? If so, including
'v2' in the subject line (easy if you use 'git format-patch -v2' or 'git
send-email -v2'), and then using this space after the --- separator to
describe what changed since v1, makes life easier for reviewers.
> scripts/checkpatch.pl | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index d1fe79bcc47c..2ca833f22e5a 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -2355,6 +2355,18 @@ sub process {
> # check for missing bracing around if etc
> if ($line =~ /(^.*)\b(?:if|while|for)\b/ &&
> $line !~ /\#\s*if/) {
> + my $allowed = 0;
> +
> + # Check the pre-context.
> + if ($line =~ /(\}.*?)$/) {
> + my $pre = $1;
> +
> + if ($line !~ /else/) {
> + print "APW: ALLOWED: pre<$pre> line<$line>\n"
> + if $dbg_adv_apw;
> + $allowed = 1;
> + }
> + }
> my ($level, $endln, @chunks) =
> ctx_statement_full($linenr, $realcnt, 1);
> if ($dbg_adv_apw) {
> @@ -2363,7 +2375,6 @@ sub process {
> if $#chunks >= 1;
> }
> if ($#chunks >= 0 && $level == 0) {
> - my $allowed = 0;
> my $seen = 0;
> my $herectx = $here . "\n";
> my $ln = $linenr - 1;
> @@ -2407,7 +2418,7 @@ sub process {
> $allowed = 1;
> }
> }
> - if ($seen != ($#chunks + 1)) {
> + if ($seen != ($#chunks + 1) && !$allowed) {
> ERROR("braces {} are necessary for all arms of this statement\n" . $herectx);
> }
> }
> --
> 2.7.4
>
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-03-19 15:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 13:56 [Qemu-devel] [PATCH RFC] scripts/checkpatch.pl: Bug fix Su Hang
2018-03-19 15:25 ` Eric Blake [this message]
2018-03-19 15:50 ` Su Hang
-- strict thread matches above, loose matches on Subject: below --
2018-03-15 11:45 Su Hang
2018-03-15 11:50 ` Peter Maydell
2018-03-15 12:06 ` Su Hang
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=938b752e-770a-b8d2-d51f-55ef412973ae@redhat.com \
--to=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=suhang16@mails.ucas.ac.cn \
--cc=vsementsov@virtuozzo.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;
as well as URLs for NNTP newsgroup(s).