[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090102113115.GA3027@elte.hu>
Date: Fri, 2 Jan 2009 12:31:15 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Sam Ravnborg <sam@...nborg.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Roland Dreier <rdreier@...co.com>,
Ian Campbell <ian.campbell@...rix.com>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>,
Helge Deller <deller@....de>,
Rusty Russell <rusty@...tcorp.com.au>,
linux-parisc <linux-parisc@...r.kernel.org>,
Linux Kernel Development <linux-kernel@...r.kernel.org>,
Kyle McMartin <kyle@...artin.ca>,
Randolph Chung <randolph@...sq.org>,
Andrew Morton <akpm@...ux-foundation.org>,
John David Anglin <dave@...uly1.hia.nrc.ca>
Subject: Re: [PATCH] parisc: fix module loading failure of large kernel
modules (take 4)
* Sam Ravnborg <sam@...nborg.org> wrote:
> > I guess I could make a sparse rule for this, but nobody seems to run
> > or care about sparse anyway. Sad.
>
> There is some increased janitorial effort recently. Try to grep for
> [Ss]+parse in the shortlog for the last couple of months.
in the x86 space there's a lot of Sparse activity as well: a number of
developers do systematic runs of Sparse and keep the tree Sparse-clean.
The moment this spreads to a critical mass of subsystems we can start
automating it. (as i was able to automate the checking of -Werr builds on
x86, with arbitrary random .config's)
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists