warnings

[Ray Lehtiniemi]

On Fri, Sep 03, 2004 at 05:01:56PM +0100, Dave Jones wrote:
> 
> I've spent the last few days playing around with sparse & xorg.
> A sort-of compiler written by Linus Torvalds, (snapshots here:
>  http://www.codemonkey.org.uk/projects/bitkeeper/sparse/)
> which outputs lots of warnings about things, but no actual code.

are these just snapshots of http://sparse.bkbits.net/, or snapshots
with your local changes as well?


> I fixed up a bunch of the K&R function headers with protoize just to
> get sparse to parse them without complaint, and have some patches pending
> for whomever is interested post-release.  I've also fixed up
> a slew of warnings that sparse outputs, and have patches for those
> also.

cool.


> There's tons of low-hanging fruit for anyone motivated here.
> >From experience with the kernel janitor project, I'd suggest just diving
> in to some random file, fixing stuff up and posting/filing bugzilla
> reports as you go along rather than trying to do a single sweep-n-clear
> operation in one go, which usually results in a half dozen people doing
> the same thing.

just checked out http://janitor.kernelnewbies.org/, very nice!  

looking at the latest patchset, is seems that a lot of it is
sweep-n-clear type of changes (min-max, list_for_each, remove-old-ifdefs)
how are those coordinated?

once a certain class of errors has been tackled and minimized, do you
guys make any attempt to prevent new errors of that type from creeping
in? or is that even feasible to do?


-- 
----------------------------------------------------------------------
     Ray L   <rayl at mail.com>