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=-10.3 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_SANE_1,WEIRD_PORT autolearn=unavailable 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 80C1FC433E0 for ; Fri, 19 Feb 2021 14:50:07 +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 346C664EB2 for ; Fri, 19 Feb 2021 14:50:07 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 346C664EB2 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.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=KSRzdKmIcD3yFaQV5j62Tyt7tQ/TzrNGGMnXWobiOqU=; b=LvYbZ0t+QwnfoXvB0xjy6MCbU hTQAQIAurkf5p/K05IfdoIt3nxitgXoNIa8kUEsyZZ19H8x/Uw+238rLt+o5FtxM3Pw1n57G8ik1P 7R3nz4iW1+b9pOuYe96WcJEVkA78Q19TS07kfqOOXe4lI/l3P9yE16FOc9IMzIeneNRDf4q6HYGCZ y563haUbZ0ezy4Hef1frSOWSynCrvunEBarbE23B2rL5EWMEhgyXyF9QNI1MD8zoFkOs7YcinX2Di yK2vIG2Z0O5zFhzScd7swTKHuEWa4npCf7OjCuyTzg1G2xPfYk+w5URk4f1lfLRgGOMRBft10t+df olFhxwgQg==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1lD746-0002Sp-1Z; Fri, 19 Feb 2021 14:47:30 +0000 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1lD742-0002Rx-MC for linux-arm-kernel@lists.infradead.org; Fri, 19 Feb 2021 14:47:27 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1613746044; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4c+qZYHckGTx1tTFDNJ70MwWPI4v8lbqr4E8l5bbSS4=; b=Bg1LWoiwiwoNLbxkJ6GOtISmpAcJUZ0szScjuhYoGZ1iotPgaHICf7Nhl3hQNKW57kLT6J R4Y7pG6FCzGXaqzaiJPeCibg/qT2xFfp4R+6Q2u2VU7qCT3/1uAJGXgHPbKlpPpkyga59q vWmQh1Kza4kLmFzz4NI9xoNQRWQHiM8= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-239-1acmZWfYNwaAHYpTRUjdiA-1; Fri, 19 Feb 2021 09:45:49 -0500 X-MC-Unique: 1acmZWfYNwaAHYpTRUjdiA-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 5BBCB3FFC; Fri, 19 Feb 2021 14:45:47 +0000 (UTC) Received: from [10.36.116.11] (ovpn-116-11.ams2.redhat.com [10.36.116.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7255D5C1C2; Fri, 19 Feb 2021 14:45:44 +0000 (UTC) Subject: Re: 5.10 LTS Kernel: 2 or 6 years? To: Hanjun Guo , Greg Kroah-Hartman , Scott Branden References: <595affb4-36e8-0a63-ebb3-a4fd0e3c243a@huawei.com> From: Nikolai Kondrashov Message-ID: <2a7ff382-1d35-0eeb-6fb6-bad37aa4c1d7@redhat.com> Date: Fri, 19 Feb 2021 16:45:42 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <595affb4-36e8-0a63-ebb3-a4fd0e3c243a@huawei.com> Content-Language: en-US X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210219_094726_872552_4C0B481F X-CRM114-Status: GOOD ( 28.47 ) 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: Yanjin , LKML , kernelci@groups.io, Huxinwei , 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 Hanjun, On 2/19/21 10:54 AM, Hanjun Guo wrote: > 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. I heard about Huawei ramping up kernel testing from someone at FOSDEM 2019. I wonder if it was you :) Nice to see your progress and the company stepping up to help with testing! Would you be interested in working with the Linux Foundation KernelCI project on submitting your build and test results to the common database - KCIDB? We are working on aggregating results from various testing systems so we can provide a dashboard, and a single, aggregated e-mail report to subscribed maintainers and developers. We have a prototype dashboard at https://staging.kernelci.org:3000/ and are working hard on making the e-mail reports good enough to start reaching out to maintainers. We already have ARM, Google Syzbot, Gentoo GKernelCI, Red Hat CKI, and, of course, KernelCI native tests sending data to the database. Linaro Tuxsuite is starting sending today. We could use your data, and of course any development help you could spare :) I wish I could show you my today's KCIDB presentation at DevConf.cz, but the recording is not out yet. Meanwhile you can take a look at our presentation at last year's Linux Plumbers: https://youtu.be/y9Glc90WUN0?t=10739 Or see our intro in an older blog post: https://foundation.kernelci.org/blog/2020/08/21/introducing-common-reporting/ Anyone wishing to contribute to KCIDB gets credentials and permissions to submit to our "playground" setup where they can send their data, see it in a dashboard, experiment without worrying about breaking anything, and decide if they like it or not. If you're interested, take a look at our Submission HOWTO: https://github.com/kernelci/kcidb/blob/v8/SUBMISSION_HOWTO.md and send an email to kernelci@groups.io (CC'd), or come over to the #kernelci channel on freenode.net! Nick On 2/19/21 10:54 AM, 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. > > 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 > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel