mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Slade Watkins <srw@sladewatkins.net>
Cc: Carl Dasantas <dasantas2020@gmail.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: New Longterm Kernel before 6.1 Rust?
Date: Wed, 5 Oct 2022 08:06:48 +0200	[thread overview]
Message-ID: <Yz0e+LF0F7wIfgvR@kroah.com> (raw)
In-Reply-To: <3034898c-a6ab-6982-aea3-656a09398ffb@sladewatkins.net>

On Wed, Oct 05, 2022 at 01:05:08AM -0400, Slade Watkins wrote:
> On 10/3/22 at 9:35 AM, Carl Dasantas wrote:
> > 
> > I was wondering if a new longterm kernel will be made prior to 6.1
> > being released with Rust support added? As the kernel.org page
> > https://www.kernel.org/category/releases.html states "Longterm kernels
> > are picked based on various factors -- major new features...". In my
> > opinion, adding Rust support is a major new feature. Of course it goes
> > on to say new longterm kernels are dependent on time, etc so I thought
> > I would inquire. No harm in that, right? I'm sure there are a lot of
> > others in our community that are hesitant as I am with Rust and want
> > to see where it goes. It would be nice to have a recent longterm
> > kernel so we can see how this Rust stuff plays out. Possibly from 6.0
> > or 5.19?
> 
> Not sure if a decision has been made yet. IMHO, it may be _a bit_ before we
> see this year's longterm release picked.

I try to make the LTS release the "last kernel of the year" unless that
turns out to have major issues (i.e. people use the LTS release as an
excuse to throw a lot of crap into it, which has happened in the past,
and almost happened here again for 6.1).

Rust has nothing at all to do with this decision, sorry.  For 6.1 it is
only a "hello world" type thing, not like you would be using Rust for
anything else in the kernel at this point in time.

hope this helps,

greg k-h

      reply	other threads:[~2022-10-05  6:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 13:35 Carl Dasantas
2022-10-05  5:05 ` Slade Watkins
2022-10-05  6:06   ` Greg KH [this message]

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=Yz0e+LF0F7wIfgvR@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dasantas2020@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@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

all inboxes | Powered by JetHome®