From: Greg KH <gregkh@linuxfoundation.org>
To: Kris Chaplin <kris.chaplin@amd.com>
Cc: Ruslan Bilovol <ruslan.bilovol@gmail.com>,
Willy Tarreau <w@1wt.eu>, Theodore Ts'o <tytso@mit.edu>,
Michal Simek <michal.simek@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Reg the next LTS kernel (6.1?)
Date: Thu, 16 Feb 2023 12:20:49 +0100 [thread overview]
Message-ID: <Y+4RkU0x9VRYcUGv@kroah.com> (raw)
In-Reply-To: <2e2c9362-1f4e-a183-e619-c5dc3e56324a@amd.com>
On Thu, Feb 16, 2023 at 10:41:01AM +0000, Kris Chaplin wrote:
> On 05/02/2023 06:27, Ruslan Bilovol wrote:
>
> > So, is there a final decision taken on what will be our next LTS?
> > Went through https://kernel.org/category/releases.html but it still shows
> > v5.15 as the latest LTS version.
>
> No announcement has been made yet on this - my understanding is that a
> greater volume and community involvement in testing and feedback is required
> to indicate the quality of 6.1 (currently 6.1.12) prior to Greg making that
> decision on behalf of the community.
Have you looked at the above link recently? :)
next prev parent reply other threads:[~2023-02-16 11:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 7:37 Reg the next LTS kernel (6.1?) Kaiwan N Billimoria
2022-10-07 7:46 ` Greg KH
2022-10-07 7:50 ` Kaiwan N Billimoria
2022-12-17 13:02 ` Kaiwan N Billimoria
2022-12-17 13:18 ` Greg KH
2022-12-17 13:44 ` Kaiwan N Billimoria
2022-12-17 16:40 ` Willy Tarreau
2022-12-20 1:45 ` Kaiwan N Billimoria
2022-12-18 8:42 ` Greg KH
2023-01-11 8:15 ` Conor Dooley
2023-01-11 11:33 ` Greg KH
2023-01-11 19:05 ` Conor Dooley
2023-01-12 12:23 ` Kris Chaplin
2023-01-12 12:26 ` Michal Simek
2023-01-13 11:27 ` Greg KH
2023-01-13 12:54 ` Michal Simek
2023-01-13 16:22 ` Greg KH
2023-01-13 21:40 ` Theodore Ts'o
2023-01-14 7:14 ` Willy Tarreau
2023-01-14 8:26 ` Greg KH
2023-01-14 8:47 ` Willy Tarreau
2023-02-05 6:27 ` Ruslan Bilovol
2023-02-16 10:41 ` Kris Chaplin
2023-02-16 11:20 ` Greg KH [this message]
2023-02-16 11:23 ` Kris Chaplin
2023-01-16 12:16 ` Michal Simek
2023-01-17 3:07 ` Theodore Ts'o
2023-01-16 12:02 ` Michal Simek
2023-01-13 11:24 ` Greg KH
2022-10-07 15:04 Carl Dasantas
2022-10-07 15:36 ` Greg KH
2022-10-07 16:07 ` Carl Dasantas
2022-10-07 16:34 ` Greg KH
2022-10-07 19:50 ` Theodore Ts'o
2022-10-07 17:37 ` Slade Watkins
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=Y+4RkU0x9VRYcUGv@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kris.chaplin@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=ruslan.bilovol@gmail.com \
--cc=tytso@mit.edu \
--cc=w@1wt.eu \
/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).