From: Sam Ravnborg <sam@ravnborg.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: sparse <linux-sparse@vger.kernel.org>
Subject: Re: Warn for extern prototypes
Date: Wed, 30 Apr 2014 22:48:16 +0200 [thread overview]
Message-ID: <20140430204816.GA14951@ravnborg.org> (raw)
In-Reply-To: <20140430203056.GJ26890@mwanda>
On Wed, Apr 30, 2014 at 11:30:57PM +0300, Dan Carpenter wrote:
> On Wed, Apr 30, 2014 at 10:07:30PM +0200, Sam Ravnborg wrote:
> > The rationale behind this is that at least in some areas of the kernel,
> > the use of "extern" for prototypes are no longer accepted.
> > A sparse warnings would be good to tell me all the cases I missed
> > in the conversion.
>
> Doesn't checkpatch.pl already check for this?
checkpatch --strict -f foo.h will include this check.
But then there are so much other noise...
It is much simpler to do:
make C=2 arch/sparc/
and the process the sparse warnings.
Sam
prev parent reply other threads:[~2014-04-30 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 20:07 Warn for extern prototypes Sam Ravnborg
2014-04-30 20:30 ` Dan Carpenter
2014-04-30 20:48 ` Sam Ravnborg [this message]
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=20140430204816.GA14951@ravnborg.org \
--to=sam@ravnborg.org \
--cc=dan.carpenter@oracle.com \
--cc=linux-sparse@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).