On 4/26/08, Adrian Bunk <bunk@xxxxxxxxxx> wrote: > On Sat, Apr 26, 2008 at 03:45:54PM +0200, Vegard Nossum wrote: > > Hi Sam, > > > > Maybe something like this could be useful for cleaning up headers (and > > maintaining that cleanliness once it has been achieved). What do you think? > > > > (One thing which might or might not be good is that 'make headerdep' will > > also compile using CC if they're not already compiled. If this should be > > fixed, I think you'd know how to do it.) > > > This way you only catch problems in the current kernel configuration. > > The only problems are under include/, and you should be able to do this > by parsing all headers and without hooking into the build system. This seems correct. Then a solution similar to 'make headers_check' should be used. Vegard -- "The animistic metaphor of the bug that maliciously sneaked in while the programmer was not looking is intellectually dishonest as it disguises that the error is the programmer's own creation." -- E. W. Dijkstra, EWD1036 -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
