> Another way to look at it... All of a sudden, different from 2.6.24, > kernel 2.6.25-git build spews so many warnings that I need to disable > section mismatch checking completely, because there is so much noise > that __normal build messages scroll off the screen__. One can ignore or one can fix... I decided to spend some of my friday on fixing section mismatch warnings as I've got a bit irritated over people spending time complaining but failing to provide patches. My work approach was to seelct a directory and fix all warnings there before moving on. So I did not as such pick the easy ones or anything like that. Despite this I managed with a one day effort to bring down the number of warnings in my build from 106 to 50 warnings. And yesterday the figure was 136. So when complaining about the number of warnings I can only say that we would all benefit if they are fixed. Just ignoring them will not sort it out. I did not pull your latest patches so my numbers are outdated for net/drivers/ which alone count for 11 out of 50 warnings in my tree. I am also eagerly awaiting Andrew to push as he has a few patches pending all over but the section mismatch warnings are the least of his worries these days. I hope to get down to less than 20 warnings in my allyesconfig build before the merge window closes. And with just a bit of assistance from others this is doable. Sam - who expected more people to actually fix this stuff :-( - To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
