Sam Ravnborg wrote:
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.
Sam - who expected more people to actually fix this stuff :-(
Well, with due respect, it's a bit presumptuous to add a bunch of warnings to the kernel build (due to more strict checking), and then get annoyed when people aren't jumping up and fixing this stuff immediately.
There were no build complaints in 2.6.24 for my stuff (libata and drivers/net) during my test builds, nor were there any for my 2.6.25-git merge window pushes, nor were there any complaints when I last checked Andrew's -mm tree.
So from our perspective, you dumped a lot of work in our laps from out of the blue, getting irritated at us along the way.
Maybe we can resolve this in a more kinder, gentler, coordinated fashion? :)
What could be done to prevent this sort of situation in the future? Maybe add these checks to -mm, and then not push your strict checking upstream until the build noise is reduced?
Jeff - 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
