From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Ben Hutchings <ben@decadent.org.uk>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] Documentation: process: update the list of current LTS
Date: Fri, 14 Oct 2022 09:08:29 +0200 [thread overview]
Message-ID: <Y0kK7WrfFutYcFzZ@kroah.com> (raw)
In-Reply-To: <20221013183414.667316-1-ndesaulniers@google.com>
On Thu, Oct 13, 2022 at 11:34:14AM -0700, Nick Desaulniers wrote:
> 3.16 was EOL in 2020.
> 4.4 was EOL in 2022.
>
> 5.10 is new in 2020.
> 5.15 is new in 2021.
>
> We'll see if 6.1 becomes LTS in 2022.
>
> Link: https://lore.kernel.org/stable/514c425e2b4dca71a11b0c669746d3122f7039a5.camel@decadent.org.uk/
> Link: https://lore.kernel.org/stable/1643877137240249@kroah.com/
> Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
> ---
> Documentation/process/2.Process.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/process/2.Process.rst b/Documentation/process/2.Process.rst
> index e05fb1b8f8b6..9ae64376a8d4 100644
> --- a/Documentation/process/2.Process.rst
> +++ b/Documentation/process/2.Process.rst
> @@ -130,12 +130,12 @@ for a longer period. As of this writing, the current long term kernels
> and their maintainers are:
>
> ====== ================================ =======================
> - 3.16 Ben Hutchings (very long-term kernel)
> - 4.4 Greg Kroah-Hartman & Sasha Levin (very long-term kernel)
> 4.9 Greg Kroah-Hartman & Sasha Levin
> 4.14 Greg Kroah-Hartman & Sasha Levin
> 4.19 Greg Kroah-Hartman & Sasha Levin
> 5.4 Greg Kroah-Hartman & Sasha Levin
> + 5.10 Greg Kroah-Hartman & Sasha Levin
> + 5.15 Greg Kroah-Hartman & Sasha Levin
> ====== ================================ =======================
>
> The selection of a kernel for long-term support is purely a matter of a
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
prev parent reply other threads:[~2022-10-14 7:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 18:34 [PATCH] Documentation: process: update the list of current LTS Nick Desaulniers
2022-10-14 2:24 ` Bagas Sanjaya
2022-10-14 7:08 ` Greg Kroah-Hartman
2022-10-14 16:34 ` Tyler Hicks
2022-10-14 16:46 ` Greg Kroah-Hartman
2022-10-14 17:10 ` [PATCH v2] Documentation: process: replace outdated LTS table w/ link Nick Desaulniers
2022-10-14 17:13 ` Tyler Hicks
2022-10-14 17:41 ` Greg Kroah-Hartman
2022-10-15 2:06 ` Bagas Sanjaya
2022-10-18 0:04 ` Nick Desaulniers
2022-10-18 3:33 ` Bagas Sanjaya
2022-10-18 21:44 ` Jonathan Corbet
2022-10-22 3:27 ` Bagas Sanjaya
2022-10-14 7:08 ` Greg Kroah-Hartman [this message]
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=Y0kK7WrfFutYcFzZ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ben@decadent.org.uk \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=sashal@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;
as well as URLs for NNTP newsgroup(s).