On 21.05.2019 2:17, Ben Pfaff wrote: > On Mon, May 20, 2019 at 04:29:39PM +0300, Ilya Maximets wrote: >> Instead of managing kernel minor versions manually we could always test >> with the most recent stable release of the desired branch. >> >> With this patch applied Travis will always check with the most recent >> kernels, so we'll be notified about changes in upstream kernels that >> breaks the build of our kernel module. However, this will also break >> Travis checks on patches that doesn't touch the kernel parts until >> we fix the module. >> >> Signed-off-by: Ilya Maximets <[email protected]> >> --- >> >> Whould like to here some opinions on this patch. >> >> Also, right now we have a broken build with recent longterm 4.9.177. >> So, this patch, probably, should not be applied before the build with >> 4.9.177 fixed. > > I think it's pretty clever and I'm generally in favor of it, but I don't > have an idea of how often the Travis checks would break. Maybe the only > easy way to find out is to try it.
I agree. I've sent rebased v2. So, we could apply it once build with 4.9.177 fixed and see what will happen. Best regards, Ilya Maximets. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
