From: Andy Whitcroft <apw@shadowen.org>
To: Dave Jones <davej@redhat.com>, Andi Kleen <andi@firstfloor.org>,
Andy Whitcroft <apw@shadowen.org>, Andrew Morton <akpm@osdl.org>,
Randy Dunlap <rdunlap@xenotime.net>,
Joel Schopp <jschopp@austin.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add a trivial patch style checker II
Date: Fri, 01 Jun 2007 15:18:43 +0100 [thread overview]
Message-ID: <46602AC3.5060309@shadowen.org> (raw)
In-Reply-To: <20070531195917.GC31153@redhat.com>
Dave Jones wrote:
> On Thu, May 31, 2007 at 02:07:53PM +0200, Andi Kleen wrote:
> > > Yeah, that is a very sensible idea.
> > >
> > > > Possible further checks that might make sense:
> > > > - panic() anywhere in drivers/*
> > > > - externs in .c files without asmlinkage
> > > > - general checking that everything in a fully visible {} block is the right
> > > > indentation
> > > >
> >
> > Here are some more warnings I would like to see:
> >
> > - Warning for any spinlock/mutex definition that doesn't have a comment
> > nearby (all locks ought to be documented)
>
> Also barriers. (Probably even moreso).
Both of these seem a pretty good idea. Should be in version 0.03 which
I'll try and get to Andrew over the weekend. Example reports from files
in 2.6.22-rc2-mm1 below.
-apw
spinlock_t definition without comment
FILE: lib/statistic.c:243:
+ spinlock_t lock;
struct mutex definition without comment
FILE: include/linux/kernelcapi.h:67:
+ struct mutex recv_mtx;
memory barrier without comment
FILE: fs/ext2/balloc.c:1250:
+ smp_rmb();
next prev parent reply other threads:[~2007-06-01 14:19 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-27 17:11 [PATCH] add a trivial patch style checker Andy Whitcroft
2007-05-27 17:10 ` Randy Dunlap
2007-05-28 10:48 ` Andy Whitcroft
2007-05-29 15:00 ` Joel Schopp
2007-05-27 17:49 ` Andreas Schwab
2007-05-27 21:49 ` Dave Jones
2007-05-28 0:18 ` Andrew Morton
2007-05-28 12:10 ` Andy Whitcroft
2007-05-28 9:13 ` Sam Ravnborg
2007-05-28 9:45 ` Jan Engelhardt
2007-05-29 9:01 ` Andy Whitcroft
2007-05-29 16:12 ` Joel Schopp
2007-05-29 16:20 ` Julio M. Merino Vidal
2007-05-29 20:00 ` Jan Engelhardt
2007-05-29 1:51 ` Qi Yong
2007-05-29 2:23 ` Andi Kleen
2007-05-29 9:05 ` Andy Whitcroft
2007-05-29 20:22 ` Jan Engelhardt
2007-05-29 22:36 ` Randy Dunlap
2007-05-30 8:34 ` Jan Engelhardt
2007-05-30 15:33 ` Randy Dunlap
2007-05-30 16:04 ` Jan Engelhardt
2007-05-31 12:07 ` [PATCH] add a trivial patch style checker II Andi Kleen
2007-05-31 19:59 ` Dave Jones
2007-06-01 14:18 ` Andy Whitcroft [this message]
2007-05-29 11:53 ` [PATCH] add a trivial patch style checker Heiko Carstens
2007-05-29 13:19 ` Andi Kleen
2007-05-29 14:22 ` Heiko Carstens
2007-05-29 14:58 ` Andi Kleen
2007-05-29 16:43 ` Heiko Carstens
2007-05-29 23:21 ` Andi Kleen
2007-05-29 18:55 ` Andy Whitcroft
2007-05-29 21:07 ` [PATCH] add a trivial patch style checker v2 Andy Whitcroft
2007-05-29 22:42 ` Joel Schopp
2007-06-06 12:40 ` Geert Uytterhoeven
2007-06-06 15:04 ` Dave Jones
2007-06-06 18:35 ` Andy Whitcroft
2007-05-31 19:26 ` [PATCH] add a trivial patch style checker Jan Engelhardt
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=46602AC3.5060309@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@osdl.org \
--cc=andi@firstfloor.org \
--cc=davej@redhat.com \
--cc=jschopp@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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