FYI, the OSDL has a "patch bot" system available that will do compile
verifications on patches.
Patches can be submitted against standard kernel releases or in a
depends-on fashion against other patches.
Six total compile configs are tried, UP & SMP of the following:
- Default config
- Desktop config (really just a bunch of stuff enabled)
- STP config (required hardware support to run on the OSDL's STP)
When the tests are done running against your patch, you get a summary
email telling you which tests passed and which ones failed.
The system is at: http://www.osdl.org/cgi-bin/plm
A sample page (kernel 2.5.47) is at:
http://www.osdl.org/cgi-bin/plm?module=patch_info&patch_id=943
Another sample (kernel 2.4.20-rc2) is at:
http://www.osdl.org/cgi-bin/plm?module=patch_info&patch_id=978
Note the filters at the bottom, clicking on the FAIL by desktop config
gives the .config used in the test followed by enough of the tail of the
compile log to tell what went wrong.
Patches in the PLM can then be used in benchmark runs in the STP.
The standard 2.4 and 2.5 trees are auto-added after they hit our ftp
mirror.
I am interested in modifying the "Desktop" config to mirror the average
user as well as putting in a new "all" when we have the ability to do
it (/lots/ of modules...) People having suggestions on what to include
in the Desktop config, please speak up.
People can also download the patch content from the patch info page.
Thanks,
Nathan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/