stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mason <slash.tmp@free.fr>
To: stable@vger.kernel.org
Cc: Sebastian Frias <sf84@laposte.net>
Subject: Next LTS release
Date: Mon, 6 Jun 2016 09:36:47 +0200	[thread overview]
Message-ID: <5755280F.1050906@free.fr> (raw)

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?

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.

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?

Regards.

             reply	other threads:[~2016-06-06  7:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06  7:36 Mason [this message]
2016-06-08  1:56 ` Next LTS release Greg KH
2016-06-08 12:59   ` Mason
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=5755280F.1050906@free.fr \
    --to=slash.tmp@free.fr \
    --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).