From: Joe Perches <joe@perches.com>
To: Cruz Julian Bishop <cruzjbishop@gmail.com>
Cc: "Ken O'Brien" <kernel@kenobrien.org>,
gregkh@linuxfoundation.org, swetland@google.com,
arve@android.com, viro@zeniv.linux.org.uk, dhowells@redhat.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: android: checkpatch.pl fixes
Date: Sat, 20 Oct 2012 19:09:04 -0700 [thread overview]
Message-ID: <1350785344.16706.6.camel@joe-AO722> (raw)
In-Reply-To: <1350785121.12361.2.camel@CruzBishop-ASPIRE>
On Sun, 2012-10-21 at 12:05 +1000, Cruz Julian Bishop wrote:
> is there currently any way to insert, say,
> a comment that filters out the next line for checkpatch
> errors?
>
> For example,
>
> /* checkpatch_ignore_(rulename) */
> (Long line that can't be broken here)
Nope. checkpatch is a stupid little tool.
It has its place, but it's a very limited one.
If you want to extend it, knock your self out...
next prev parent reply other threads:[~2012-10-21 2:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 22:33 [PATCH 1/2] staging: android: checkpatch.pl fixes Ken O'Brien
2012-10-20 22:33 ` [PATCH 2/2] staging: android: binder.c: checkpatch.pl Ken O'Brien
2012-10-21 1:05 ` [PATCH 1/2] staging: android: checkpatch.pl fixes Joe Perches
2012-10-21 2:05 ` Cruz Julian Bishop
2012-10-21 2:09 ` Joe Perches [this message]
2012-10-22 9:37 ` David Howells
2012-10-22 12:15 ` Joe Perches
2012-10-22 13:02 ` Peter Hurley
2012-10-22 13:16 ` [PATCH] checkpatch: Warn on unnecessary line continuations Joe Perches
2012-10-22 16:45 ` Joe Perches
2012-10-28 4:46 ` [PATCH v2] " Joe Perches
2012-10-22 20:03 ` [PATCH 1/2] staging: android: checkpatch.pl fixes Greg KH
2012-10-24 14:48 ` kernel kernel
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=1350785344.16706.6.camel@joe-AO722 \
--to=joe@perches.com \
--cc=arve@android.com \
--cc=cruzjbishop@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@kenobrien.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swetland@google.com \
--cc=viro@zeniv.linux.org.uk \
/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