Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp172630pxb; Fri, 19 Feb 2021 23:05:35 -0800 (PST) X-Google-Smtp-Source: ABdhPJx9z5MJIzPqDhtYHR/D2eIhRRWfctSjCKcYAwF6u7hPs0cC/kaOgelNbQEnfew6biz1dnYc X-Received: by 2002:a17:906:3a13:: with SMTP id z19mr12454747eje.317.1613804735307; Fri, 19 Feb 2021 23:05:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613804735; cv=none; d=google.com; s=arc-20160816; b=KqEHc3uPyRkTGGBa88ZmHIhQRcg1TDs4Lj3S2o0KOut7P9UpZDR6T2/yyFO+Ttzybw 3HVsrOcEjigULTO4l1k+T8LDItvTDArbbNZ0V8WgYRyRSCsY9lqMoq4NvgK6wZGuEGUq pYcZB8vVWFFKOKYZA1EW0AhxjFiRM5vIKORam/w51UoqZ9VKiGN/XLvOetuBNj13KLqM a5aw0zIQFnXoMTuDlMCIervNrN54T8qJJo2w2sbk9FknWyV7odiN02FJrkupxV5j2UDS jy9gOW4e3SFrOgzvvSJ2ZlBaRnfFvL1t4lGOc7M3IKiU2UmT/uNH48BDOfHPPm6Zh0Lc 7jgQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=vm6RnYPfMIDTJEdLsFKT0ulP1HUyLfyrRLgRlK6HTMY=; b=xO/Hj7P4m2PZSeXWLz/Nk6PwBs81QH4NPKODqZHadCvaw6L8LwLC7t2xCF8cF7Ai5W 9++gaqHjKqBh94Y7BCL2Wb8ZLLex7bEj2bZBTe9yiYzx1k4Wg2HU8S4cScBsXqdnNcne BKDhjEc0VuUTu+gkY/gnZOqMwQ9bsG6Fu9OB+tDtHGvbFtpqcFkcz0jxDCwo6ZqbeKjz dXdvOTReNtXf+K9+IsJoJbI6ZxIfByUykdFAZtttpcVECPRMawnxl9pwmIbcD3gtnsaf QQ1XCqrc4Qc4KCTa3kTjOv0nGN12Pvy/NitrQCQ0v2FJqZGT2kNuhfxFxdNacU2lZPxE 93KQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id jr2si7694932ejb.129.2021.02.19.23.05.12; Fri, 19 Feb 2021 23:05:35 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229811AbhBTHDt (ORCPT + 99 others); Sat, 20 Feb 2021 02:03:49 -0500 Received: from szxga05-in.huawei.com ([45.249.212.191]:12984 "EHLO szxga05-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229614AbhBTHDp (ORCPT ); Sat, 20 Feb 2021 02:03:45 -0500 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 CC: Scott Branden , BCM Kernel Feedback , LKML , Linux ARM , PEIXIN HOU , Yanjin , "Zhangdianfang (Dianfang, OS Lab)" , Zhaohongjiang , Huxinwei , Wei Yongjun 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-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Originating-IP: [10.174.178.147] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.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