Dear Andreas,
In message 4E9D4552.5040506@gmail.com you wrote:
We should first get a state of "all boards build clean" for a sort of toolchains (I think arm is now at this state after a lot of tumult in the last two releases).
PowerPC has traditionally always been build-clean (all boards succeed to build, with very few [2...3] causing harmelss build warnings). Now ARM is close to that, too. MIPS has also always been building mostly fine.
This is some kind of CI as suggested by Lukasz Majewski. I also favor CI for fast feedback to the submitter if his change breaks something.
I'm not sure how to do that. To provide feedback to individual submitters, you would have to runn a full build cycle for each patch we apply. That would obviously be best, but I don't have machine power to do that.
What I do is testing batches - say, after applying 20...30 patches, or after major changes.
I have Jenkins running every night for a few selected CPU families, which already catches a number of issues, but even then it's directly pointing to a submitted patch.
I guess it will be doable to have some scripts/prepare-patch which runs a) git format-patch b) checkpatch on the patch c) (configurable subset of) MAKEALL on some clean tree with that patch applied d) append the results to the patch
This tool would implement some kind of CI but utilize the computing power of submitter.
Sounds good. Any takers?
Best regards,
Wolfgang Denk