From: Joe Perches <joe@perches.com>
To: "Levin, Alexander" <alexander.levin@verizon.com>
Cc: Sasha Levin <levinsasha928@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: checkkpatch (in)sanity ?
Date: Sat, 27 Aug 2016 19:20:54 -0700 [thread overview]
Message-ID: <1472350854.26978.51.camel@perches.com> (raw)
In-Reply-To: <1472348579.26978.47.camel@perches.com>
On Sat, 2016-08-27 at 18:42 -0700, Joe Perches wrote:
> 46 WARNING:LONG_LINE_COMMENT
> 45 WARNING:LEADING_SPACE
> 37 WARNING:LONG_LINE
> 16 ERROR:GIT_COMMIT_ID
> 11 WARNING:COMMIT_LOG_LONG_LINE
> 5 WARNING:BRACES
> 2 WARNING:BAD_SIGN_OFF
> 2 WARNING:AVOID_BUG
> 2 ERROR:SPACING
> 1 WARNING:SPLIT_STRING
> 1 WARNING:FILE_PATH_CHANGES
> 1 WARNING:ENOSYS
> 1 ERROR:MISSING_SIGN_OFF
My copy/pasta mistake, the above was Ingo Molnar's list
Here's Linus'
37 WARNING:LONG_LINE
19 ERROR:GIT_COMMIT_ID
8 WARNING:PREFER_PR_LEVEL
6 ERROR:SPACING
4 WARNING:MACRO_WITH_FLOW_CONTROL
3 WARNING:COMMIT_LOG_LONG_LINE
2 WARNING:TYPO_SPELLING
2 WARNING:BAD_SIGN_OFF
2 ERROR:TRAILING_STATEMENTS
1 WARNING:NEW_TYPEDEFS
1 WARNING:LONG_LINE_COMMENT
1 WARNING:LINE_SPACING
1 WARNING:CONSTANT_COMPARISON
1 WARNING:AVOID_BUG
1 ERROR:STABLE_ADDRESS
next prev parent reply other threads:[~2016-08-28 2:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 20:40 checkkpatch (in)sanity ? Joe Perches
2016-08-28 1:06 ` Levin, Alexander
2016-08-28 1:42 ` Joe Perches
2016-08-28 2:20 ` Joe Perches [this message]
2016-08-28 2:47 ` Levin, Alexander
2016-08-28 17:15 ` Joe Perches
2016-08-28 17:59 ` Greg KH
2016-08-28 22:37 ` Levin, Alexander
2016-08-28 23:20 ` Joe Perches
2016-08-29 2:22 ` Levin, Alexander
2016-08-29 8:20 ` Christoph Hellwig
2016-08-29 7:15 ` [Ksummit-discuss] " Alexandre Belloni
2016-08-29 9:01 ` Arnd Bergmann
2016-08-29 12:47 ` Joe Perches
2016-08-29 17:16 ` Josh Triplett
2016-08-29 17:41 ` Joe Perches
2016-08-29 17:46 ` Luck, Tony
2016-08-29 18:01 ` Joe Perches
2016-08-29 18:47 ` Joe Perches
2016-08-29 19:08 ` Josh Triplett
2016-08-29 21:07 ` Arnd Bergmann
2016-08-29 11:15 ` Kalle Valo
2016-08-29 12:30 ` Joe Perches
2016-08-29 18:01 ` Kalle Valo
2016-08-29 19:00 ` Joe Perches
2016-08-29 21:00 ` [Ksummit-discuss] " Arnd Bergmann
2016-08-28 7:56 ` Alexey Dobriyan
2016-08-28 9:59 ` Julia Lawall
2016-08-28 19:52 ` Joe Perches
2016-08-28 20:35 ` Jiri Kosina
2016-08-28 21:24 ` Dennis Kaarsemaker
2016-08-28 21:57 ` Joe Perches
2016-08-29 19:06 ` Dan Carpenter
2016-08-29 19:10 ` Josh Triplett
2016-08-29 19:17 ` Dan Carpenter
2016-08-29 19:34 ` Joe Perches
2016-08-29 19:21 ` Joe Perches
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=1472350854.26978.51.camel@perches.com \
--to=joe@perches.com \
--cc=alexander.levin@verizon.com \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=levinsasha928@gmail.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;
as well as URLs for NNTP newsgroup(s).