From: Mason <slash.tmp@free.fr>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org, Sebastian Frias <sf84@laposte.net>
Subject: Re: Next LTS release
Date: Wed, 8 Jun 2016 14:59:33 +0200 [thread overview]
Message-ID: <575816B5.7090009@free.fr> (raw)
In-Reply-To: <20160608015625.GB26618@kroah.com>
On 08/06/2016 03:56, Greg KH wrote:
> On Mon, Jun 06, 2016 at 09:36:47AM +0200, Mason wrote:
>> Hello,
>>
>> I read the kernel summit summary.
>> https://lwn.net/Articles/662966/
>>
>> I was wondering if the 4.4 release set a "precedent" in that the
>> next few LTS releases going forward would be aimed for early Q1?
>
> Probably.
Bummer.
>> The reason I'm asking is that my company plans to release an SDK
>> in Q4, and I was hoping to bundle a recent kernel.
>
> Nothing preventing you from always just advancing your kernel to the
> latest LTS one when it comes out, right?
Some customers, once they have something working, they don't want
to change anything. If I release a v4.4-based SDK, and then such
a customer comes along, I'll be stuck having to support v4.4 until
my beard is grey.
(I was told we are still expected to support several 2.6 kernels.)
>> I currently provide 4.4 but most of my port was accepted in later
>> versions. I was hoping I wouldn't need to backport all that code.
>>
>> What do the tea leaves say?
>
> Something in Q1, no idea what number specifically, but if all of your
> code is already merged upstream, it doesn't really matter what you pick,
> anything will end up working for you.
The platform code got merged in 4.5 and 4.6 but I'm still missing
several important (but non-essential) drivers. Thus 4.4 isn't really
helpful to me, I'd have to port everything.
By the way, looking at the LTS releases, it seems some (older) releases
are supported longer than others (3.16, 3.12, 3.10, 3.4, 3.2). Is that
because some are supported by other groups/distros? (IIUC, many Android
devices run 3.4 and 3.10)
https://www.kernel.org/category/releases.html
Regards.
next prev parent reply other threads:[~2016-06-08 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 7:36 Next LTS release Mason
2016-06-08 1:56 ` Greg KH
2016-06-08 12:59 ` Mason [this message]
2016-06-08 15:22 ` Greg KH
2016-06-08 18:14 ` Willy Tarreau
2016-06-08 21:39 ` Mason
2016-06-08 22:04 ` Willy Tarreau
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=575816B5.7090009@free.fr \
--to=slash.tmp@free.fr \
--cc=greg@kroah.com \
--cc=sf84@laposte.net \
--cc=stable@vger.kernel.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).