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]

Date:   Wed, 11 Jan 2023 12:33:38 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Conor Dooley <conor.dooley@...rochip.com>
Cc:     Kaiwan N Billimoria <kaiwan.billimoria@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Reg the next LTS kernel (6.1?)

On Wed, Jan 11, 2023 at 08:15:23AM +0000, Conor Dooley wrote:
> Hey Greg,
> 
> You didn't ask me specifically, but if it helps...

It really really does, thank you!

> On Sat, Dec 17, 2022 at 02:18:30PM +0100, Greg KH wrote:
> > On Sat, Dec 17, 2022 at 06:32:48PM +0530, Kaiwan N Billimoria wrote:
> > > Hi,
> > > Any update on 6.1 being set as the next LTS release?
> > 
> > You tell me please.  How has your testing gone for 6.1 so far?
> > Does it work properly for you?
> 
> AFIACT, it does. We had some issues, but they've since been resolved.

Great!

> > Are you and/or your company willing to test out
> > the -rc releases and provide feedback if it works or not for your
> > systems?
> 
> Already do! Although so far I've just been reporting breakages rather
> than providing tested-bys.

Feel free to submit a tested-by if you want credit for doing the work
(and so that I know it still is working), I'm more than glad to collect
them all as they end up in the release commit message in the kernel log.
One example can be seen here:
	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.1.y&id=2cb8e624295ffa0c4d659fcec7d9e7a6c48de156

> > Do you have problems with 6.1.y vs. older kernels?
> 
> Nope, anything that needed fixing that was on my radar has already made
> it into 6.1.y.
> 
> > Is there
> > anything missing in it that you feel needs to be addressed with a newer
> > kernel instead?
> 
> Anything missing on the RISC-V side of things, that we would want, is
> still a work in progress for kernels later than 6.2 anyway.

that's great to hear, thanks for letting me know and for testing.

greg k-h