From: "Theodore Ts'o" <tytso@mit.edu>
To: Carl Dasantas <dasantas2020@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
kaiwan.billimoria@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: Reg the next LTS kernel (6.1?)
Date: Fri, 7 Oct 2022 15:50:12 -0400 [thread overview]
Message-ID: <Y0CC9IfhWj+/DXTp@mit.edu> (raw)
In-Reply-To: <CANNVxH_fDjD2TU0ccW19hSKXwTL+m6kDPr6n7=36uipStgwzGA@mail.gmail.com>
On Fri, Oct 07, 2022 at 12:07:05PM -0400, Carl Dasantas wrote:
> It's moreso the fact that initial Rust support is being added. Yes I
> know it's just initial support/NVMe drivers.
Care to name a *single* functional kernel feature (whether a device
driver or not) that is dependent on RUST. Have you tried building the
latest development kernel without rust --- what happens? (hint: nothing)
> Also, Rust support isn't the only major
> change in 6.1, by the kernel.orgs own site (time permitting) an LTS is
> made if major changes are present.
This is simply not true. The start of a new LTS kernel has always
been time-based, and there certainly have been attempts to get new
major functionality around this time of year in the hopes that it can
be made avcailable in distro kernels. Of course, if the functionality
or change is too flaky, it could very well get reverted or the
distributions will simply not enable the feature because it would be a
support nightmare for them.
All of this does not apply for Rust. Again, take a look at what is
*actually* been included during the current merge window.
Regards,
- Ted
next prev parent reply other threads:[~2022-10-07 19:50 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
2022-10-07 16:07 ` Carl Dasantas
2022-10-07 16:34 ` Greg KH
2022-10-07 19:50 ` Theodore Ts'o [this message]
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=Y0CC9IfhWj+/DXTp@mit.edu \
--to=tytso@mit.edu \
--cc=dasantas2020@gmail.com \
--cc=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 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).