Received: by 2002:a05:6358:a55:b0:ec:fcf4:3ecf with SMTP id 21csp359276rwb; Sat, 14 Jan 2023 01:25:05 -0800 (PST) X-Google-Smtp-Source: AMrXdXua+KN3Ud6be2ayRzMB93QdAHv0iyiKINxnSx5owZztxUYkBodRuCbxEW2PP7jC+IIfVIJb X-Received: by 2002:a17:907:7a0d:b0:78d:f455:c398 with SMTP id mg13-20020a1709077a0d00b0078df455c398mr60814338ejc.62.1673688305405; Sat, 14 Jan 2023 01:25:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673688305; cv=none; d=google.com; s=arc-20160816; b=twg/pUOsQs4DT5zfIv8YuA4MQhxZxdFDF6jpCC05v8J3ZwKmIWjNnVZj7HRXAadeV3 9vuq/PFqD/95nkJoZ7YuvZbtJYThMCsnNdnfhi9Ss16K+/54PLL/VJw60mUr7tD19FZT aFbfu3O39KNxMqGGpvL+KXl6SJpZXfhEgycWLPSa5n+82D0MTdAWWHB3m9F6agMhrlOC hu3VKsVA8hNmzuYsDwM4jtkXS+UiCK1ulQQZv0wyrcKQQBLpEWelEJqC5fOHOUs+4x1Q ydptgbGeOhEaTQqWXjJNoGwkbBwDwtDHyozkuSCE14kojjYGElxCphG7mD1BAM8CY9x/ 6Uuw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=ABeTN0dpMeygu07EUvMpYZVodjwh4ohGFeDQHNg9JDU=; b=T16rOialZFL5ZCR4MZEa5Ju/Yxe/gq/Yqtfm/Z8DNiLRyDz+1fxsHYMF41k6ChRWJr XLgPMCCyTEE4ylAX//MhcWFpbF2HwVS5QJEkFSMaconyCeZyru6oujCHmVNVvC89d00t UtW9McSrrHXlBkrpTnvgokQciHpJq7FEIOGTbXNP89uZVAl/0VpfhczkrsjDYr1PytRW CT7oXGxt3msG0kPpsghGSS5jogGV5ixmedMXQR+cFUH9lpBdm8I43eTMM58RUG0uES2A wYahrH9TKdzvCzM2A9yrnnL7jTpFYS3cg7RRIwoj2RRazTD/gRLEVGHXwJcHm0t/+ShL G2Og== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id xi8-20020a170906dac800b00782ff2649a7si685503ejb.346.2023.01.14.01.24.52; Sat, 14 Jan 2023 01:25:05 -0800 (PST) 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; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229674AbjANIr2 (ORCPT + 53 others); Sat, 14 Jan 2023 03:47:28 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40502 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229500AbjANIr0 (ORCPT ); Sat, 14 Jan 2023 03:47:26 -0500 Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 57DEF4EC2 for ; Sat, 14 Jan 2023 00:47:25 -0800 (PST) Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id 30E8lJUw006072; Sat, 14 Jan 2023 09:47:19 +0100 Date: Sat, 14 Jan 2023 09:47:19 +0100 From: Willy Tarreau To: Greg KH Cc: "Theodore Ts'o" , Michal Simek , Kris Chaplin , Linux Kernel Mailing List Subject: Re: Reg the next LTS kernel (6.1?) Message-ID: <20230114084719.GA6057@1wt.eu> References: <96e41e6d-bec9-f8cf-22ed-1fa5d9022238@amd.com> <314489f6-cb54-fb3b-6557-d69b1284fa4d@amd.com> <20230114071412.GB5088@1wt.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS, SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jan 14, 2023 at 09:26:07AM +0100, Greg KH wrote: > On Sat, Jan 14, 2023 at 08:14:12AM +0100, Willy Tarreau wrote: > > On Fri, Jan 13, 2023 at 04:40:19PM -0500, Theodore Ts'o wrote: > > > On Fri, Jan 13, 2023 at 05:22:56PM +0100, Greg KH wrote: > > > > > I am just saying that developers/driver owners can simple do calculation to > > > > > identify LTS version. When they know it they also know time when their > > > > > deadline is for upstreaming work. It means if patch is accepted between > > > > > 6.0-r1 and 6.0-rc5/6 they know that it will get to 6.1 merge window. > > > > > > > > That is what I am afraid of and if it causes problems I will purposfully > > > > pick the previous release. This has happened in the past and is never > > > > an excuse to get anything merged. Code gets merged when it is ready, > > > > not based on a LTS release. > > > > > > This is probably the best reason not to preannounce when the LTS > > > release will be ahead of time --- because it can be abused by > > > developers who try to get not-ready-for-prime-time features into what > > > they think will be the LTS kernel, with the result that the last > > > release of the year could be utterly unsitable for that perpose. > > > > We know this risk exists but since Greg never makes promises on any > > version, it remains reasonable. > > I have to _not_ make promises because in the past when I did, people > threw crap into the kernel with the "justification" that they had to get > it in this specific kernel because it was going to be the LTS one. > > We can't have nice things, because people abuse it :( Absolutely, that was exactly my point :-) And quite frankly it's better the current way, because you have the flexibility to change your mind on a given version if during the first months you discover it's too crappy and will be a maintenance nightmare. Willy