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 9D496C433E0 for ; Sat, 20 Feb 2021 07:04:58 +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 4D7AA64EB8 for ; Sat, 20 Feb 2021 07:04:58 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4D7AA64EB8 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=WKdKLUehDW3xf8q5SiG03EtIlkC7VfqlZjTmF2ngp3M=; b=nH1TZR7ZQnMtTl8R03QR6xqhM uVuX4UpebmD0iH3/8v7rJxcvJs/3qOsC3YYPrUXACc1Q5sUgo7xB093wKwAtC+fQZ5OQWKC8RVHY9 DYOFyQ0XkYsOSH80bdrowZJ+olBgXmGvlUkyGKYW0n7jG4/MDLfw6h2GkPw+ESrOne+D2ezVrDjN6 +M7Yska6exmPvTVhZVeHN1cZUXIYGDOt2jixWAQ898sebPjFVVZM4MfKIgdAFo8qnQLl60wr26Xdd Ul4cqyzl+/ktlqWmNdtr01oSKHnzzivQHwBrWLvAgBy4mRllIn3obQ/1iO5+ni/5PKoWyJs/GYQK1 NO846678w==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1lDMIN-0007PS-Lb; Sat, 20 Feb 2021 07:03:15 +0000 Received: from szxga05-in.huawei.com ([45.249.212.191]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1lDMIJ-0007Oq-Iy for linux-arm-kernel@lists.infradead.org; Sat, 20 Feb 2021 07:03:13 +0000 Received: from DGGEMS409-HUB.china.huawei.com (unknown [172.30.72.59]) by szxga05-in.huawei.com (SkyGuard) with ESMTP id 4DjK9k2V7BzjQLY; Sat, 20 Feb 2021 15:01:30 +0800 (CST) Received: from [10.174.178.147] (10.174.178.147) by DGGEMS409-HUB.china.huawei.com (10.3.19.209) with Microsoft SMTP Server id 14.3.498.0; Sat, 20 Feb 2021 15:02:54 +0800 Subject: Re: 5.10 LTS Kernel: 2 or 6 years? To: Greg Kroah-Hartman References: <595affb4-36e8-0a63-ebb3-a4fd0e3c243a@huawei.com> From: Hanjun Guo Message-ID: Date: Sat, 20 Feb 2021 15:02:54 +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-20210220_020312_175091_E57C14D3 X-CRM114-Status: GOOD ( 24.26 ) 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 , Scott Branden , LKML , Yanjin , BCM Kernel Feedback , Zhaohongjiang , "Zhangdianfang \(Dianfang, OS Lab\)" , Wei Yongjun , 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 On 2021/2/19 17:08, Greg Kroah-Hartman wrote: > On Fri, Feb 19, 2021 at 04:54:24PM +0800, Hanjun Guo wrote: >> 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. > > Wonderful! > >> 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. > > Great! Do you all need an email notification when the -rc releases come > out for the stable trees, or can you trigger off of the -rc stable git > tree? Different CI systems work in different ways :) We can trigger the test when you updated the -rc stable git tree, by monitoring new commits for the stable branches. So if you push all the commits at once for -rc stable branches, then our CI system can work well. > > And if you can reply to the -rc release emails with a "Tested-by:" tag, > I will be glad to add that to the release commit when that happens to > show that you all have tested the release. Thanks, will reply "Tested-by:" with -rc releases. We are working on setting up the test farm and will report the test results in a week. > >> And we will start from ARM64 and X86 architecture first, and then extend >> to other platforms. > > That's a good start, the useful ones :) > >> 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. > > That's fine, it is not something that happens at a regular interval. > >> Does this sound good to you? > > Yes it does, thank you so much. > > greg k-h Thanks Hanjun _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel