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 X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 476E7C433E0 for ; Mon, 22 Feb 2021 14:02:29 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id DD4B664E2E for ; Mon, 22 Feb 2021 14:02:28 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DD4B664E2E Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=digitalocean.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=whsfw12SDQrEHUVaHYmis9uW9P8cKSeziS7iU1lIi4s=; b=JPQ/2+svCx/0TeE1keMH+zHD1 Vl2fRZJmtlQ9BbqAaEzExD+nxuvXWUNILy8LI1v7FXKT4OrZtLCF6q7LlWNkjpyRYDZ1/SBgPTXxN o2Vd8r31O/v3MylIl8x8/Mb+oykXs08CktXh70goztfn0jP7aznuKFh+bYUZImf3zQSWlBfi7Ufo9 CCsnn1im12dSKHJf4InQHChzyNbbcku6EgUEmFPrBT2y0z71xOLU5BE+favXmMe4/Wu4d6nw57aUv 5u8DG1cBMAJdxuXP8EcY7SuQBPMbc93SnUYlN7KRjtE09DjQYRA6JWsFTpmHCuD/BjIabymxfn4Oe HWTurSqNA==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1lEBln-0003D2-Qq; Mon, 22 Feb 2021 14:01:03 +0000 Received: from mail-qt1-x833.google.com ([2607:f8b0:4864:20::833]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1lEBlk-0003Bf-73 for linux-arm-kernel@lists.infradead.org; Mon, 22 Feb 2021 14:01:02 +0000 Received: by mail-qt1-x833.google.com with SMTP id z6so8692160qts.0 for ; Mon, 22 Feb 2021 06:00:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=digitalocean.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=HA3GKOGorULqJ9zOscJLMbtGbrtN/SqWQvqLlzI6tz8=; b=Ze3yohCevrSiwjuZedC7tnZp4jFlgosfELUXLjAy1O+h1Uc6iEoI4Kc6AByOFom6u4 4VooOdpmTSg3HuEXFZa0yY4t+SDVP1bs3BtluHFuKYrtccmyFcFeg0rTprJbWNroEfOf NTpl5ZKDLn5Re0tO8TcVDf60sD0lf0apZT6yQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=HA3GKOGorULqJ9zOscJLMbtGbrtN/SqWQvqLlzI6tz8=; b=XoFF+2ikLkuhAluA4BaOa7c2QVeXlbWLHin2X+UQoRdWFDJWljiv16oUOQ5viK2rPH NAkZ2hKa2gUO4+X7eWAKR5hW3rZ8P7Ekb5iGtVMZFXZ2V3D6lSPt4A75pRyBVlk4Yd3T 5vJlKmMBfJGWGruUrPMS/zz0VzDGU31LvfwvdshJO+Cu2qMRfCV1nq5qXSSD+ejUgwl/ wVKnrLgVtWXiyKbajXqlih0y0idFMRavbKYg4qTFCtvHb9Y/TleOEiKZhvADx+RWOowo 5aeHb3pk1y+u9CfzUgkqQ3EEBxeHpwTiAGG6O6EXNiFL/j66skwXVYpAujPmlLchLFCM yT3Q== X-Gm-Message-State: AOAM53089SWygugxpqPNG1Scx8hM2iTTW9/WvpcY5aDfO2Xt77mIauZs ir6F+2ilrsr+cuffBrXn8f0Dsg== X-Google-Smtp-Source: ABdhPJyu7V/n0QSfvFBTfWYz/By9ws4KCuMYZsO/oeLNcQ6NLt1A4WDZHqlOI647xi/GwYytvGG3Zg== X-Received: by 2002:ac8:1208:: with SMTP id x8mr20126292qti.14.1614002455257; Mon, 22 Feb 2021 06:00:55 -0800 (PST) Received: from breakout.internal.digitalocean.com ([2600:1700:7aa0:1690:e583:b823:e3cc:4987]) by smtp.gmail.com with ESMTPSA id o17sm9221766qki.100.2021.02.22.06.00.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 22 Feb 2021 06:00:54 -0800 (PST) Received: by breakout.internal.digitalocean.com (Postfix, from userid 1000) id DBD888AAE4C; Mon, 22 Feb 2021 08:00:52 -0600 (CST) Date: Mon, 22 Feb 2021 08:00:52 -0600 From: Nishanth Aravamudan To: Greg Kroah-Hartman Subject: Re: 5.10 LTS Kernel: 2 or 6 years? Message-ID: <20210222140052.GA1520276@breakout> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210222_090100_367528_B1A10C2D X-CRM114-Status: GOOD ( 23.10 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Scott Branden , pmccormick@digitalocean.com, LKML , BCM Kernel Feedback , Linux ARM , cgardner@digitalocean.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Greg, On 26.01.2021 [08:29:25 +0100], Greg Kroah-Hartman wrote: > On Mon, Jan 25, 2021 at 11:55:11AM -0800, Scott Branden wrote: > > Hi All, > > > > The 5.10 LTS kernel being officially LTS supported for 2 years > > presents a problem: why would anyone select a 5.10 kernel with 2 > > year LTS when 5.4 kernel has a 6 year LTS. > > If 5.10 is "actually" going to be supported for 6 years it would be > > quite valuable to make such a declaration. > > https://www.kernel.org/category/releases.html > > Why? What would that change? > > Ok, seriously, this happens every year, and every year we go through > the same thing, it's not like this is somehow new, right? > > I want to see companies _using_ the kernel, and most importantly, > _updating_ their devices with it, to know if it is worth to keep > around for longer than 2 years. I also, hopefully, want to see how > those companies will help me out in the testing and maintenance of > that kernel version in order to make supporting it for 6 years > actually possible. > > So, are you planning on using 5.10? Will you will be willing to help > out in testing the -rc releases I make to let me know if there are any > problems, and to help in pointing out and backporting any specific > patches that your platforms need for that kernel release? > > When I get this kind of promises and support from companies, then I am > glad to bump up the length of the kernel support from 2 to 6 years, > and I mark it on the web site. Traditionally this happens in > Febuary/March once I hear from enough companies. Can I count on your > support in this endeavor? I am very sorry for the long delay on my end (I had privately e-mailed Greg on January 28) -- DigitalOcean also intends to provide feedback and testing on the 5.10 series. We intend to use it as the basis for our next-next kernel and are very invested in ensuring the stability and performance of the kernel. Thanks, Nish _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel