From: Joe Perches <joe@perches.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: apw@canonical.com, linux-kernel@vger.kernel.org,
davem@davemloft.net, netdev@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] checkpatch.pl: Fix warnings on (networking specific) code comments
Date: Sun, 27 Jan 2013 09:11:07 -0800 [thread overview]
Message-ID: <1359306667.14406.7.camel@joe-AO722> (raw)
In-Reply-To: <1359286539-18395-1-git-send-email-jeffrey.t.kirsher@intel.com>
On Sun, 2013-01-27 at 03:35 -0800, Jeff Kirsher wrote:
> This patch reverts a portion of the commit to allow multi-line code
> comments to use either style.
[]
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -1878,13 +1878,6 @@ sub process {
> }
>
> if ($realfile =~ m@^(drivers/net/|net/)@ &&
> - $rawline =~ /^\+[ \t]*\/\*[ \t]*$/ &&
> - $prevrawline =~ /^\+[ \t]*$/) {
> - WARN("NETWORKING_BLOCK_COMMENT_STYLE",
> - "networking block comments don't use an empty /* line, use /* Comment...\n" . $hereprev);
> - }
> -
> - if ($realfile =~ m@^(drivers/net/|net/)@ &&
> $rawline !~ m@^\+[ \t]*\*/[ \t]*$@ && #trailing */
> $rawline !~ m@^\+.*/\*.*\*/[ \t]*$@ && #inline /*...*/
> $rawline !~ m@^\+.*\*{2,}/[ \t]*$@ && #trailing **/
Shrug.
Ignore things you don't agree with.
David has written many, many emails
requesting changes for this specific
comment style.
I think you and Intel should use
--ignore=NETWORKING_BLOCK_COMMENT_STYLE
to avoid seeing this if you don't agree
with it.
I also think expectations that everyone
will agree with every checkpatch bleat
are unrealistic.
next prev parent reply other threads:[~2013-01-27 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 11:35 [PATCH] checkpatch.pl: Fix warnings on code comments Jeff Kirsher
2013-01-27 17:11 ` Joe Perches [this message]
2013-01-27 23:59 ` David Miller
2013-01-28 2:56 ` Jeff Kirsher
2013-01-28 3:07 ` David Miller
2013-01-28 17:17 ` Allan, Bruce W
2013-01-28 17:30 ` Joe Perches
2013-01-28 20:56 ` Jeff Kirsher
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=1359306667.14406.7.camel@joe-AO722 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).