<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 17, 2016 at 1:48 PM, Greg KH <span dir="ltr"><<a href="mailto:greg@kroah.com" target="_blank">greg@kroah.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, May 17, 2016 at 04:27:35PM -0400, <a href="mailto:Valdis.Kletnieks@vt.edu">Valdis.Kletnieks@vt.edu</a> wrote:<br>
> On Tue, 17 May 2016 13:09:03 -0700, Michael Harless said:<br>
><br>
> > > Eeek, why? What is keeping you from moving to a newer kernel version?<br>
> > > Why is sticking with 3.14 a good idea for anyone?<br>
> > ><br>
> ><br>
> > It's mainly due to certifications and testing and our upgrade process. My<br>
> > wish would be to update to a new kernel as well.<br>
><br>
> That's a very broken certification system, if it allows you to attach<br>
> pretty much random patches onto a "blessed" 3.14 kernel, but won't let<br>
> you upgrade to a newer kernel<br>
<br>
</span>You beat me to it :)<br>
<span class=""><br>
> Thought Experiment: What happens if you take a standard 3.14 kernel, and apply<br>
> *every single* patch from 3.15 from Linus's tree except the one that actually<br>
> tags it as 3.15?<br>
<br>
</span>Hey, wait, some other distro did that once, and guess what, no one<br>
noticed! So other distros finally got wise and just gave up the charade<br>
and now do full kernel updates on incremental releases, with no reported<br>
problems at all (i.e. SuSE and Oracle.)<br>
<br>
So, just grab the 4.4 kernel tree and patch the makefile to say it is<br>
3.14 and you should pass the certification system just fine!<br>
<br></blockquote><div><br></div><div>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.</div><div><br></div><div>--Mike</div><div><br></div></div></div></div>