Patches to intel-gpu-tools are very much welcome, we really want this to be the universal set of low-level tools and testcases for the Intel kernel gfx driver on Linux and similar platforms. So please bring on porting patches, bugfixes, improvements for documentation and new tools and testcases. A short list of contribution guidelines: - Please submit patches formatted with git send-email/git format-patch or equivalent to Intel GFX discussion Please use --subject-prefix="PATCH i-g-t" so that i-g-t patches are easily identified in the massive amount mails on intel-gfx. To ensure this is always done, autogen.sh will run: git config format.subjectprefix "PATCH i-g-t" on its first invocation. - intel-gpu-tools is MIT lincensed and we require contributions to follow the developer's certificate of origin: http://developercertificate.org/ - When submitting new testcases please follow the naming conventions documented in the generated documentation. Also please make full use of all the helpers and convenience macros provided by the igt library. The semantic patch lib/igt.cocci can help with the more automatic conversions. - Patches need to be reviewed on the mailing list. Exceptions only apply for testcases and tooling for drivers with just a single contributor (e.g. vc4). In this case patches must still be submitted to the mailing list first. Testcase should preferrably be cross-reviewed by the same people who write and review the kernel feature itself. - When patches from new contributors (without commit access) are stuck, for anything related to the regular releases, issues with packaging and integrating platform support or any other intel-gpu-tools issues, please contact one of the maintainers (listed in the MAINTAINERS file) and cc the intel-gfx mailing list. - Especially changes to the testcase should get tested on relevant platforms before committing. For Intel employees that's best done using PRTS, see the relevant internal howtos. Everyone else can just run piglit with i-g-t tests locally. Happy hacking!