Thread (7 messages) 7 messages, 3 authors, 2016-05-17

How to locally maintain an end-of-life kernel branch?

From: Michael Harless <hidden>
Date: 2016-05-17 20:53:29

On Tue, May 17, 2016 at 1:48 PM, Greg KH [off-list ref] wrote:
On Tue, May 17, 2016 at 04:27:35PM -0400, Valdis.Kletnieks at vt.edu wrote:
quoted
On Tue, 17 May 2016 13:09:03 -0700, Michael Harless said:
quoted
quoted
Eeek, why?  What is keeping you from moving to a newer kernel
version?
quoted
quoted
quoted
Why is sticking with 3.14 a good idea for anyone?
It's mainly due to certifications and testing and our upgrade
process.  My
quoted
quoted
wish would be to update to a new kernel as well.
That's a very broken certification system, if it allows you to attach
pretty much random patches onto a "blessed" 3.14 kernel, but won't let
you upgrade to a newer kernel
You beat me to it :)
quoted
Thought Experiment:  What happens if you take a standard 3.14 kernel,
and apply
quoted
*every single* patch from 3.15 from Linus's tree except the one that
actually
quoted
tags it as 3.15?
Hey, wait, some other distro did that once, and guess what, no one
noticed!  So other distros finally got wise and just gave up the charade
and now do full kernel updates on incremental releases, with no reported
problems at all (i.e. SuSE and Oracle.)

So, just grab the 4.4 kernel tree and patch the makefile to say it is
3.14 and you should pass the certification system just fine!
I'll look into that.  I've also got some 3rd party proprietary drivers
(ugh), that I'd have to see would work or not.

--Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160517/54d5e63b/attachment-0001.html 
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help