From: Peter Maydell <peter.maydell@linaro.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: Mike Day <ncmike@ncultra.org>, Blue Swirl <blauwirbel@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Don Slutz <dslutz@verizon.com>
Subject: Re: [Qemu-devel] [PATCH] Update QEMU checkpatch.pl to current linux version
Date: Thu, 8 May 2014 15:02:16 +0100 [thread overview]
Message-ID: <CAFEAcA-q5UKaKhj5dVsZSqpFgwtRJUc+Vn6bPir2oEc0FCQS4A@mail.gmail.com> (raw)
In-Reply-To: <87zjisjrqt.fsf@blackfin.pond.sub.org>
On 8 May 2014 14:59, Markus Armbruster <armbru@redhat.com> wrote:
> Don Slutz <dslutz@verizon.com> writes:
>> I have used to following to see how a new version compares:
>>
>>
>> k=500;i=0;j=0;for sha in $(git log --no-merges --format=format:"%h"
>> -$k);do let i=$i+1; git show $sha >/tmp/a; clear;echo $i;head -20
>> /tmp/a; ./scripts/checkpatch.pl --root=. /tmp/a; err=$?; if [ $err !=
>> 0 ]; then let j=$j+1;read foo;fi; done;echo Check $i, Bad $j
>>
>> ...
>> total: 0 errors, 0 warnings, 79 lines checked
>>
>> /tmp/a has no obvious style problems and is ready for submission.
>> Check 500, Bad 52
>
> How does your new checkpatch compare to our current one?
Yes; we do sometimes let checkpatch-failing commits through,
so it would be more interesting to know:
* how many commits passed old-checkpatch but fail the new one
* how many commits failed with old-checkpatch but pass now
* in both cases, how many of the failures are false positives?
(the last of those is tricky to answer without eyeballing
the errors, unfortunately)
thanks
-- PMM
next prev parent reply other threads:[~2014-05-08 14:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 18:16 [Qemu-devel] [PATCH] Update QEMU checkpatch.pl to current linux version Mike Day
2014-05-06 18:28 ` Peter Maydell
2014-05-06 18:59 ` Mike Day
2014-05-06 19:20 ` Peter Maydell
2014-05-07 21:16 ` Hani Benhabiles
2014-05-08 14:58 ` Mike Day
2014-05-08 12:43 ` Don Slutz
2014-05-08 13:59 ` Markus Armbruster
2014-05-08 14:02 ` Peter Maydell [this message]
2014-05-08 15:22 ` Mike Day
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=CAFEAcA-q5UKaKhj5dVsZSqpFgwtRJUc+Vn6bPir2oEc0FCQS4A@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=armbru@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=dslutz@verizon.com \
--cc=ncmike@ncultra.org \
--cc=qemu-devel@nongnu.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).