From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hanjun Guo <guohanjun@huawei.com>
Cc: Scott Branden <scott.branden@broadcom.com>,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
PEIXIN HOU <PEIXIN.HOU@huawei.com>,
Yanjin <yanjin.yan@huawei.com>,
"Zhangdianfang (Dianfang, OS Lab)" <zhangdianfang@huawei.com>,
Zhaohongjiang <zhaohongjiang@huawei.com>,
Huxinwei <huxinwei@huawei.com>,
Wei Yongjun <weiyongjun1@huawei.com>
Subject: Re: 5.10 LTS Kernel: 2 or 6 years?
Date: Sat, 20 Feb 2021 10:53:34 +0100 [thread overview]
Message-ID: <YDDcHpmAWmzQcStD@kroah.com> (raw)
In-Reply-To: <a0e56fe4-8e85-d8c7-ed63-7a96c0944aaf@huawei.com>
On Sat, Feb 20, 2021 at 03:02:54PM +0800, Hanjun Guo wrote:
> 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.
I do push to the -rc branches, but those branches are rebased, and I do
"intermediate" pushes as well. Meaning I push to have CI systems run on
the existing patch queue at times that are not only the "main" -rc
release periods.
Watch the branches for a few weeks to get an idea of how they work if
you are curious.
> > 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.
Great, thanks!
greg k-h
next prev parent reply other threads:[~2021-02-20 9:54 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 19:55 5.10 LTS Kernel: 2 or 6 years? Scott Branden
2021-01-26 2:50 ` Adam Borowski
2021-01-26 7:29 ` Greg Kroah-Hartman
2021-01-26 17:35 ` Florian Fainelli
2021-01-26 18:30 ` Scott Branden
2021-01-26 18:51 ` Greg Kroah-Hartman
2021-01-26 20:15 ` Willy Tarreau
2021-02-17 9:40 ` Greg Kroah-Hartman
2021-02-17 19:48 ` Scott Branden
2021-02-18 7:43 ` Greg Kroah-Hartman
2021-02-18 11:31 ` Willy Tarreau
2021-02-18 14:15 ` Jari Ruusu
2021-02-18 14:29 ` Greg Kroah-Hartman
2021-02-18 20:55 ` Pavel Machek
2021-02-18 22:43 ` Ondrej Zary
2021-02-19 8:00 ` Pavel Machek
2021-02-19 8:30 ` Greg Kroah-Hartman
2021-02-18 14:33 ` Willy Tarreau
2021-02-18 17:19 ` Jari Ruusu
2021-02-18 17:22 ` Russell King - ARM Linux admin
2021-02-18 17:44 ` Greg Kroah-Hartman
2021-02-19 7:10 ` Jari Ruusu
2021-02-19 8:22 ` Greg Kroah-Hartman
2021-02-19 10:31 ` Jari Ruusu
2021-02-19 10:37 ` Greg Kroah-Hartman
2021-02-19 10:57 ` Jari Ruusu
2021-02-19 11:16 ` Greg Kroah-Hartman
2021-02-19 15:23 ` Jari Ruusu
2021-02-20 13:29 ` Jari Ruusu
2021-02-20 16:05 ` Greg Kroah-Hartman
2021-02-20 17:06 ` Willy Tarreau
2021-02-21 11:38 ` Jari Ruusu
2021-02-19 16:50 ` Theodore Ts'o
2021-02-18 17:16 ` Florian Fainelli
2021-02-18 12:51 ` Pavel Machek
2021-02-18 16:51 ` Sasha Levin
2021-02-18 17:21 ` Florian Fainelli
2021-02-18 17:53 ` Greg Kroah-Hartman
2021-02-18 17:57 ` Florian Fainelli
2021-02-18 18:20 ` Willy Tarreau
2021-02-18 18:36 ` Greg Kroah-Hartman
2021-02-18 20:16 ` Scott Branden
2021-02-18 21:00 ` Willy Tarreau
2021-02-18 22:38 ` Scott Branden
2021-02-18 21:39 ` Sasha Levin
2021-02-18 22:00 ` Florian Fainelli
2021-02-18 22:26 ` Scott Branden
2021-02-19 8:25 ` Greg Kroah-Hartman
2021-02-19 15:05 ` Florian Fainelli
2021-02-19 15:53 ` Greg Kroah-Hartman
2021-02-19 17:44 ` Florian Fainelli
2021-02-22 14:17 ` Greg Kroah-Hartman
2021-02-18 17:42 ` Florian Fainelli
2021-02-18 18:13 ` Willy Tarreau
2021-02-18 10:04 ` Pavel Machek
2021-02-19 8:54 ` Hanjun Guo
2021-02-19 9:08 ` Greg Kroah-Hartman
2021-02-20 7:02 ` Hanjun Guo
2021-02-20 9:53 ` Greg Kroah-Hartman [this message]
2021-02-23 2:14 ` Hanjun Guo
2021-02-19 14:45 ` Nikolai Kondrashov
2021-02-26 8:03 ` Hanjun Guo
2021-02-26 11:21 ` Nikolai Kondrashov
2021-02-22 14:00 ` Nishanth Aravamudan
2021-02-22 14:24 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YDDcHpmAWmzQcStD@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=PEIXIN.HOU@huawei.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=guohanjun@huawei.com \
--cc=huxinwei@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.branden@broadcom.com \
--cc=weiyongjun1@huawei.com \
--cc=yanjin.yan@huawei.com \
--cc=zhangdianfang@huawei.com \
--cc=zhaohongjiang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox