From: Greg KH <gregkh@linuxfoundation.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: [PATCH] 4.9 is a longterm kernel
Date: Thu, 19 Jan 2017 14:48:38 +0100 [thread overview]
Message-ID: <20170119134838.GA18291@kroah.com> (raw)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Might as well just mark it as such now, to head off the constant
questions. Yes, 4.9 is the next longterm supported kernel version.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
diff --git a/content/releases.rst b/content/releases.rst
index 3c2eb973f66b..efe10dc05a8f 100644
--- a/content/releases.rst
+++ b/content/releases.rst
@@ -40,6 +40,7 @@ Longterm
======== ==================== ============ ==================
Version Maintainer Released Projected EOL
======== ==================== ============ ==================
+ 4.9 Greg Kroah-Hartman 2016-12-11 Jan, 2019
4.4 Greg Kroah-Hartman 2016-01-10 Feb, 2018
4.1 Sasha Levin 2015-06-21 Sep, 2017
3.18 Sasha Levin 2014-12-07 Jan, 2017
diff --git a/pelicanconf.py b/pelicanconf.py
index a38ba7826489..cfbde607e6cf 100644
--- a/pelicanconf.py
+++ b/pelicanconf.py
@@ -24,7 +24,7 @@ import sys
sys.path.append('./')
from plugins import releases
-LONGTERM_KERNELS = ('4.4', '4.1', '3.18', '3.16', '3.14', '3.12', '3.10', '3.4', '3.2')
+LONGTERM_KERNELS = ('4.9', '4.4', '4.1', '3.18', '3.16', '3.14', '3.12', '3.10', '3.4', '3.2')
EOL_KERNELS = ('3.14', '3.19', '4.0', '4.2', '4.3', '4.5', '4.6', '4.7', '4.8')
GIT_MAINLINE = '/mnt/git-repos/repos/pub/scm/linux/kernel/git/torvalds/linux.git'
next reply other threads:[~2017-01-19 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 13:48 Greg KH [this message]
2017-01-19 16:21 ` [PATCH] 4.9 is a longterm kernel Konstantin Ryabitsev
2017-01-19 16:31 ` 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=20170119134838.GA18291@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--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