From: Yan Hong <clouds.yan@gmail.com>
To: apw@canonical.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] scripts/checkpatch.pl: seperate mutiple results with black line
Date: Wed, 26 Sep 2012 19:41:23 +0800 [thread overview]
Message-ID: <1348659683-9202-1-git-send-email-clouds.yan@gmail.com> (raw)
Before:
total: 0 errors, 0 warnings, 14 lines checked
XXXX.patch has no obvious style problems and is ready for submission.
total: 0 errors, 0 warnings, 7 lines checked
XXXX.patch has no obvious style problems and is ready for submission.
total: 0 errors, 0 warnings, 25 lines checked
XXXX.patch has no obvious style problems and is ready for submission.
After:
total: 0 errors, 0 warnings, 14 lines checked
XXXX.patch has no obvious style problems and is ready for submission.
total: 0 errors, 0 warnings, 7 lines checked
XXXX.patch has no obvious style problems and is ready for submission.
total: 0 errors, 0 warnings, 25 lines checked
XXXX.patch has no obvious style problems and is ready for submission.
Also leave two blank lines after the error message if check fails.
Signed-off-by: Yan Hong <clouds.yan@gmail.com>
---
scripts/checkpatch.pl | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index ca05ba2..15d9f08 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -3588,7 +3588,7 @@ sub process {
print "$filename " if ($summary_file);
print "total: $cnt_error errors, $cnt_warn warnings, " .
(($check)? "$cnt_chk checks, " : "") .
- "$cnt_lines lines checked\n";
+ "$cnt_lines lines checked";
print "\n" if ($quiet == 0);
}
@@ -3617,7 +3617,7 @@ sub process {
}
if ($clean == 1 && $quiet == 0) {
- print "$vname has no obvious style problems and is ready for submission.\n"
+ print "$vname has no obvious style problems and is ready for submission.\n\n"
}
if ($clean == 0 && $quiet == 0) {
print << "EOM";
@@ -3625,6 +3625,8 @@ $vname has style problems, please review.
If any of these errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
+
+
EOM
}
--
1.7.9.5
reply other threads:[~2012-09-26 11:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1348659683-9202-1-git-send-email-clouds.yan@gmail.com \
--to=clouds.yan@gmail.com \
--cc=apw@canonical.com \
--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