linux-kernel - Re: Reg the next LTS kernel (6.1?)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAPDLWs9KWKs_-fpAp2=97uBARYqrHSYTPEU6RbqtWjAD8NpqgQ@mail.gmail.com>
Date:   Fri, 7 Oct 2022 13:20:24 +0530
From:   Kaiwan N Billimoria <kaiwan.billimoria@...il.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Reg the next LTS kernel (6.1?)

Thanks Greg.. will wait for it!

On Fri, Oct 7, 2022 at 1:15 PM Greg KH <gregkh@...uxfoundation.org> wrote:
>
> 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