Research integration with patchwork
As suggested by @mchehab
On a separate matter, Upstream patchwork (which is what we use on media) has support for integration with CI.
It is currently disabled because we didn't have so far horse power available to it. So, while the fields are there at the database, I removed viewing it, to not pollute the interface with fields that aren't used.
Now that we have more horse power, It seems the time to have a workflow that will look at the patch series sent to the ML, test compilation on CI and send back the results to both the patch author and to patchwork.
Updating in patchwork is done by using "pwclient check-create".
Internally, patchwork stores 4 results (3 of them are visible at the default web interface):
S = success
W = warning
F = fail
pending
You can see the 3 visible fields S/W/F at Kernel patchwork instance:
https://patchwork.kernel.org/project/linux-media/list/
By having CI auto-checking submitted patch series, we'll alleviate the overload over the media maintainers, as there won't be any need to review already-broken patchsets, which helps to reduce the latency on patch reviews.