From: Greg KH <gregkh@linuxfoundation.org>
To: Kaiwan N Billimoria <kaiwan.billimoria@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Reg the next LTS kernel (6.1?)
Date: Fri, 7 Oct 2022 09:46:32 +0200 [thread overview]
Message-ID: <Yz/ZWBeNZvKenEVM@kroah.com> (raw)
In-Reply-To: <CAPDLWs-Z8pYkwQ13dEgHXqSCjiq4xVnjuAXTy26H3=8NZCpV_g@mail.gmail.com>
On Fri, Oct 07, 2022 at 01:07:54PM +0530, Kaiwan N Billimoria wrote:
> Greetings!
> I'm working on the 2nd edition of the Linux Kernel Programming book
> (https://www.amazon.com/gp/product/B07RW915K4/ref=dbs_a_def_rwt_bibl_vppi_i0)
> and request your help...
>
> I'd like to base the book upon as recent a kernel version as is
> feasible, of course, with the caveat that it's a long-term (LTS) one
> that will be around for a while. Currently, the 5.10 LTS kernel's EOL
> date - Dec 2026 - makes it an ideal candidate.
>
> However, if possible, I'd (also) like to use a 6.x kernel; so, my
> question comes down to this: will a 6.1 kernel release occur soon (I
> heard it should be around Dec this year)? Will it be an LTS kernel
> (again, should be I guess), and, if so, very important for me, what's
> the likely EOL date?
I usually pick the "last kernel of the year", and based on the normal
release cycle, yes, 6.1 will be that kernel. But I can't promise
anything until it is released, for obvious reasons.
thanks,
greg k-h
next prev parent reply other threads:[~2022-10-07 7:46 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
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=Yz/ZWBeNZvKenEVM@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kaiwan.billimoria@gmail.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.