Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CANNVxH_uwnz31kak4fKAVuj8UP4wbWcFiDQ+kFwTametBvixGA@mail.gmail.com>
 <Y0BHYPat6L+FZFGQ@kroah.com>
In-Reply-To: <Y0BHYPat6L+FZFGQ@kroah.com>
From:   Carl Dasantas <dasantas2020@gmail.com>
Date:   Fri, 7 Oct 2022 12:07:05 -0400
Message-ID: <CANNVxH_fDjD2TU0ccW19hSKXwTL+m6kDPr6n7=36uipStgwzGA@mail.gmail.com>
Subject: Re: Reg the next LTS kernel (6.1?)
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     kaiwan.billimoria@gmail.com, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

It's moreso the fact that initial Rust support is being added. Yes I
know it's just initial support/NVMe drivers. The point is that it is a
major change to have another language support added. 6.0 to 6.1 is
clearly the cut off between no Rust at all and *intiail* Rust support.
I wasn't around back when C++ was added and ejected, but what was the
process then? An LTS that is very old prior to C++ > C++ added
*intiially* LTS made > C++ ejected? For those that might have been
hesitant on C++ they could have stayed on an LTS right before C++ was
added and then just skipped any potential issues and went right to the
next LTS after it was removed. 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. In my opinion, which I am sure
means nothing to most of you but echoes a lot of others, if anything
as a gesture of goodwill towards the community an LTS should be made
prior to any Rust support being added aka 5.19 or 6.0.

Carl

On Fri, Oct 7, 2022 at 11:35 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> 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