From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 53552C433F5 for ; Fri, 7 Oct 2022 19:50:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229916AbiJGTuV (ORCPT ); Fri, 7 Oct 2022 15:50:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59244 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229491AbiJGTuT (ORCPT ); Fri, 7 Oct 2022 15:50:19 -0400 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CF5FD4CA25 for ; Fri, 7 Oct 2022 12:50:17 -0700 (PDT) Received: from cwcc.thunk.org (pool-173-48-120-46.bstnma.fios.verizon.net [173.48.120.46]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 297JoCDA008062 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 7 Oct 2022 15:50:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1665172213; bh=F3+KxvdxYbXXYL5Hb3QcEbLoY4S1F7GRg9bQWulklWQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=mN75GxtK8Eteotnq4Rvju6OPcA08aupPcp0TEfrOmkJ3OIgujvOUcg8PSZlj9QnQp uKtCoqBdLb+S75ltky/DLZhbIkUvQmvQldBRsgIoZnNj/jwa13v7hrkZupWel3mQQ6 p0UK5ibADM+yYy7krw82brY+KHOfzW0iAzBEaY+JiSk9b7Z2uuhgy6ZzVti5vSvwnH dbczVkb/ZfF9Xo9l4S5m7/kqJIokK7se07T0F4Es+8j6rLiCGrbbqN3/sXclACmgwd tULQ7yiiwSsN3x8sH3Jx3KGQwqEE5W5vzLf4ggESnlDKl8LEQ0hfYiDfIcZ7tW6GCS LLJTlxtaotKqg== Received: by cwcc.thunk.org (Postfix, from userid 15806) id 1E89A15C35F2; Fri, 7 Oct 2022 15:50:12 -0400 (EDT) Date: Fri, 7 Oct 2022 15:50:12 -0400 From: "Theodore Ts'o" To: Carl Dasantas Cc: Greg KH , kaiwan.billimoria@gmail.com, linux-kernel@vger.kernel.org Subject: Re: Reg the next LTS kernel (6.1?) Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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