Folks, we have a age old dance of random parties, in particular the embedded folks, ending up with random ancient kernels on embedded devices. I've tried to carefully document a few ideas on why and how I believe we can make automatic kernel backporting scale [0] and part of this will be to try to bring consensus about a unified front to persuade users, partners, customers, whatever, to be at least on a kernel listed as supported on kernel.org. Today we backport down to the last 30 kernels, from 2.6.24 up to 3.14 and while this is manageable right now I expect the number of supported drivers and features to keep increasing (I've stopped counting). I am very aware of the reasons to support a slew of old kernels, but its nothing but our own fault for not educating enough about the importance on upgrading. I realize this is an age old issue, but since I think we need scale backports and wish to remove older kernels from it fast, I wanted to see if any folks might have ideas on what can help here other than saying, 'if you use Linux backports, your drivers will be automatically backported and supported'. To start off -- what's the *last* kernel you realistically need for your users to use backports right now? Is it really 2.6.25? Would anyone kick and scream if for the backports-3.15 release try take things up to support only down to least 3.0 *right now* ? [0] http://www.do-not-panic.com/2014/04/automatic-linux-kernel-backporting-with-coccinelle.html Luis -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
