From: Greg KH <gregkh@linuxfoundation.org>
To: Carl Dasantas <dasantas2020@gmail.com>
Cc: kaiwan.billimoria@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: Reg the next LTS kernel (6.1?)
Date: Fri, 7 Oct 2022 17:36:00 +0200 [thread overview]
Message-ID: <Y0BHYPat6L+FZFGQ@kroah.com> (raw)
In-Reply-To: <CANNVxH_uwnz31kak4fKAVuj8UP4wbWcFiDQ+kFwTametBvixGA@mail.gmail.com>
On Fri, Oct 07, 2022 at 11:04:04AM -0400, Carl Dasantas wrote:
> Please reconsidrer using 6.1 as the next LTS.
>
> 6.0 or 5.19 is much more fitting due to not having Rust support, a
> major change.
That makes no sense at all given what Rust code will be in 6.1. Did you
look at it? What specific functionality does it provide that is going
to be a problem for ANY platform that Linux currently supports?
greg k-h
next prev parent reply other threads:[~2022-10-07 15:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 15:04 Reg the next LTS kernel (6.1?) Carl Dasantas
2022-10-07 15:36 ` Greg KH [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2022-10-07 7:37 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
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
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=Y0BHYPat6L+FZFGQ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dasantas2020@gmail.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