From: Josh Triplett <josh@joshtriplett.org>
To: Joe Perches <joe@perches.com>, akpm@linux-foundation.org
Cc: Manfred Spraul <manfred@colorfullife.com>,
Andy Whitcroft <apw@canonical.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] checkpatch: Add tests for function pointer style misuses
Date: Thu, 26 Dec 2013 16:58:35 -0800 [thread overview]
Message-ID: <20131227005835.GA10986@leaf> (raw)
In-Reply-To: <52bcaaaa.D88khTPM+2orJGqY%akpm@linux-foundation.org> <20131226200723.GA7267@leaf>
On Thu, Dec 26, 2013 at 12:07:23PM -0800, Josh Triplett wrote:
> On Thu, Dec 26, 2013 at 11:20:28AM -0800, Joe Perches wrote:
> > Kernel style uses function pointers in this form:
> > "type (*funcptr)(args...)"
> >
> > Emit warnings when this function pointer form isn't used.
> >
> > Signed-off-by: Joe Perches <joe@perches.com>
>
> Two comments below.
On Thu, Dec 26, 2013 at 02:16:10PM -0800, akpm@linux-foundation.org wrote:
> The patch titled
> Subject: checkpatch: add tests for function pointer style misuses
> has been added to the -mm tree. Its filename is
> checkpatch-add-tests-for-function-pointer-style-misuses.patch
Here's a patch that fixes the two messages I commented about, which
applies on top of the version of the patch that went into -mm.
---8<---
From: Josh Triplett <josh@joshtriplett.org>
Subject: [PATCH] Fix up messages from "checkpatch: Add tests for function pointer style misuses"
Fix an ambiguity in one warning message and a copy/paste problem in
another.
Signed-off-by: Josh Triplett <josh@joshtriplett.org>
---
scripts/checkpatch.pl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 2460094..b74b086 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -2831,7 +2831,7 @@ sub process {
if (defined $pre_pointer_space &&
$pre_pointer_space =~ /^\s/) {
WARN("SPACING",
- "Unnecessary space after function pointer open parenthesis\n" . $herecurr);
+ "Unnecessary space between open parenthesis and '*' in function pointer declaration\n" . $herecurr);
}
# unnecessary space "type (* funcptr)(args...)"
@@ -2852,7 +2852,7 @@ sub process {
if (defined $pre_args_space &&
$pre_args_space =~ /^\s/) {
WARN("SPACING",
- "Unnecessary space before function pointer name\n" . $herecurr);
+ "Unnecessary space before function pointer argument list\n" . $herecurr);
}
if (show_type("SPACING") && $fix) {
--
1.8.5.2
next prev parent reply other threads:[~2013-12-27 0:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 19:20 [PATCH 0/5] checkpatch: A few corrections and updates Joe Perches
2013-12-26 19:20 ` [PATCH 1/5] checkpatch: Add tests for function pointer style misuses Joe Perches
2013-12-26 20:07 ` Josh Triplett
2013-12-27 0:58 ` Josh Triplett [this message]
2013-12-27 1:25 ` Joe Perches
2013-12-26 19:20 ` [PATCH 2/5] checkpatch: Add a --fix-inplace option Joe Perches
2013-12-26 20:08 ` Josh Triplett
2013-12-26 19:20 ` [PATCH 3/5] checkpatch: Improve space before tab --fix option Joe Perches
2013-12-26 19:20 ` [PATCH 4/5] checkpatch: check for if's with unnecessary parentheses Joe Perches
2013-12-26 20:09 ` Josh Triplett
2013-12-26 19:20 ` [PATCH 5/5] checkpatch: Update the FSF/GPL address check 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=20131227005835.GA10986@leaf \
--to=josh@joshtriplett.org \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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