Re: Automated testing for stable kernel branches?

On 10/18/18 2:31 PM, Greg KH wrote:

...

I am working on a project at Red Hat where we do quick testing on patches for internal kernels before they merge. The goal is to catch bugs or issues before they merge into kernel trees and avoid situations where kernels need time-consuming bisects when lots of patches are merged at once. We aim to put valuable feedback into a kernel developer's inbox within four hours.

Yeah!

One more quick question: When should we send emails?

Should they only be sent when a test fails? Or, should they be sent every time (even for success)?

Thanks!

-- Major Hayden