linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: Kaiwan N Billimoria <kaiwan.billimoria@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Reg the next LTS kernel (6.1?)
Date: Wed, 11 Jan 2023 12:33:38 +0100	[thread overview]
Message-ID: <Y76eklrASMczPLY0@kroah.com> (raw)
In-Reply-To: <Y75wGwt2r8iWlCYf@wendy>

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

  reply	other threads:[~2023-01-11 11:38 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 [this message]
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
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=Y76eklrASMczPLY0@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=conor.dooley@microchip.com \
    --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 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).