From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to locally maintain an end-of-life kernel branch?
Date: Tue, 17 May 2016 13:48:58 -0700 [thread overview]
Message-ID: <20160517204858.GA26243@kroah.com> (raw)
In-Reply-To: <31550.1463516855@turing-police.cc.vt.edu>
On Tue, May 17, 2016 at 04:27:35PM -0400, Valdis.Kletnieks at vt.edu wrote:
> On Tue, 17 May 2016 13:09:03 -0700, Michael Harless said:
>
> > > Eeek, why? What is keeping you from moving to a newer kernel version?
> > > Why is sticking with 3.14 a good idea for anyone?
> > >
> >
> > It's mainly due to certifications and testing and our upgrade process. My
> > 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 :)
> Thought Experiment: What happens if you take a standard 3.14 kernel, and apply
> *every single* patch from 3.15 from Linus's tree except the one that actually
> 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!
best of luck,
greg k-h
next prev parent reply other threads:[~2016-05-17 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 18:21 How to locally maintain an end-of-life kernel branch? Michael Harless
2016-05-17 19:31 ` Greg KH
2016-05-17 20:09 ` Michael Harless
2016-05-17 20:27 ` Valdis.Kletnieks at vt.edu
2016-05-17 20:48 ` Greg KH [this message]
2016-05-17 20:53 ` Michael Harless
2016-05-17 20:50 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160517204858.GA26243@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).