From: Joe Perches <joe@perches.com>
To: Daniel Walker <danielwa@cisco.com>,
Andy Whitcroft <apw@canonical.com>,
open list <linux-kernel@vger.kernel.org>,
Daniel Walker <dwalker@fifo99.com>,
"xe-kernel@external.cisco.com" <xe-kernel@external.cisco.com>
Subject: Re: checkpatch false positon on EXPORT_SYMBOL
Date: Thu, 31 Mar 2016 12:21:36 -0700 [thread overview]
Message-ID: <1459452096.1744.12.camel@perches.com> (raw)
In-Reply-To: <56FD3BAE.1070209@cisco.com>
On Thu, 2016-03-31 at 08:01 -0700, Daniel Walker wrote:
> The below looks like normal code but the last export symbol gets the
> warning,
>
>
> WARNING:EXPORT_SYMBOL: EXPORT_SYMBOL(foo); should immediately follw its
> function/variable
> #16: FILE: kernel/acct.c:70:
> +EXPORT_SYMBOL(test_export); /* Error ! */
>
> It seems to have to do with the comments at the end of the line. The
> first two examples don't have warnings because I removed the comments on
> different lines. comments on the variable and export symbol lines gets
> the error tho.
That looks like a false positive I'll leave for Andy.
$ cat ~/export_symbol.c
int test_export_no_comment;
EXPORT_SYMBOL(test_export_no_comment);
int test_export_comment_int; /* comment int */
EXPORT_SYMBOL(test_export_int);
int test_export_comment_symbol;
EXPORT_SYMBOL(test_export_symbol); /* comment symbol */
int test_export_both; /* comment both 1 */
EXPORT_SYMBOL(test_export_both); /* comment both 2 */
$
Something's a bit off with the $stat variable:
test_export_int doesn't match the EXPORT_SYMBOL test.
test_export_symbol and test_export_both get warnings.
next prev parent reply other threads:[~2016-03-31 19:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 15:01 checkpatch false positon on EXPORT_SYMBOL Daniel Walker
2016-03-31 19:21 ` Joe Perches [this message]
2016-04-11 21:51 ` Daniel Walker
2016-04-11 22:09 ` Joe Perches
2016-04-12 12:59 ` Andy Whitcroft
2016-04-12 13:37 ` Daniel Walker
2016-04-12 17:49 ` Joe Perches
2016-04-12 18:02 ` Daniel Walker
2016-04-13 6:53 ` Andy Whitcroft
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=1459452096.1744.12.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=danielwa@cisco.com \
--cc=dwalker@fifo99.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xe-kernel@external.cisco.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