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=-5.3 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 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 BBE72C433E0 for ; Fri, 19 Feb 2021 08:56:19 +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 4471F64E5C for ; Fri, 19 Feb 2021 08:56:19 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4471F64E5C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=huawei.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-Type: Content-Transfer-Encoding:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date:Message-ID:From: References:To:Subject:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=tttpdJ7sCx2JGchd2Zku/aZFnDKoM6eagKDXvw2jL8s=; b=gmcKVILiuZGh4mF5peQvEYQef HAJh+M4xn6pEc68bF79FQap/eKVCia9nzg7dHpE+4nTMQDxLac3gFUFUlQy/7NGwHwM9jF8vKYW4N jU0yaZgIoD53pxyw3pkTdfGi1GPk6J068RL7JzUDsc2yNyMUNwyD1lC7QQ127VyObbPqBt6OvEaw4 LNqND2179852sb5Kxjv3A5kmPYWVyl6hLHky7HhYpsuNoYgE+96+YAo/dh2WbHdVUikjusBG/qncP e8tLAo4eMrniNpWTWNejb4vu7kVQxxROhJPC2RL7b0yPa1cZqgRwT4ZcIDlSCqjo6fmHfaUdh9P16 1WzdhZhlQ==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1lD1Yj-0000cs-WE; Fri, 19 Feb 2021 08:54:46 +0000 Received: from szxga06-in.huawei.com ([45.249.212.32]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1lD1Yh-0000c8-Nu for linux-arm-kernel@lists.infradead.org; Fri, 19 Feb 2021 08:54:44 +0000 Received: from DGGEMS404-HUB.china.huawei.com (unknown [172.30.72.59]) by szxga06-in.huawei.com (SkyGuard) with ESMTP id 4DhljB2ByCzjNVp; Fri, 19 Feb 2021 16:53:18 +0800 (CST) Received: from [10.174.178.147] (10.174.178.147) by DGGEMS404-HUB.china.huawei.com (10.3.19.204) with Microsoft SMTP Server id 14.3.498.0; Fri, 19 Feb 2021 16:54:24 +0800 Subject: Re: 5.10 LTS Kernel: 2 or 6 years? To: Greg Kroah-Hartman , Scott Branden References: From: Hanjun Guo Message-ID: <595affb4-36e8-0a63-ebb3-a4fd0e3c243a@huawei.com> Date: Fri, 19 Feb 2021 16:54:24 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-GB X-Originating-IP: [10.174.178.147] X-CFilter-Loop: Reflected X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210219_035444_082755_721D7129 X-CRM114-Status: GOOD ( 15.00 ) 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: Huxinwei , LKML , Yanjin , BCM Kernel Feedback , Zhaohongjiang , "Zhangdianfang \(Dianfang, OS Lab\)" , PEIXIN HOU , Linux ARM Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Greg, On 2021/1/26 15:29, Greg Kroah-Hartman wrote: [...] > > 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? We(Huawei) are willing to commit resources to help out in testing the stable -rc releases, and to help to backport patches for stable kernels. 5.10 stable kernel will be used for openEuler [1] kernel and also inside Huawei. From customer's feedback, it's very important to see the stable kernel we used to be maintained for 6 years in the community, and we will use 5.10 kernel for at least 6 years, so we are willing to help you and help ourselves :) In specific, we will start from the testing work, using HULK robot (reports lots of bugs to mainline kernel) testing framework to test compile, reboot, functional testing, and will extend to basic performance regression testing in the future. And we will start from ARM64 and X86 architecture first, and then extend to other platforms. For patch backporting, will send the bugfix patches (from mainline) we spotted, but I think this work may not doing in regular but will be triggered as needed. Does this sound good to you? Thanks Hanjun [1]: https://openeuler.org/en/ _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel