From: Florian Fainelli <email@example.com> To: Sasha Levin <firstname.lastname@example.org>, Scott Branden <email@example.com> Cc: Greg Kroah-Hartman <firstname.lastname@example.org>, BCM Kernel Feedback <email@example.com>, LKML <firstname.lastname@example.org>, Linux ARM <email@example.com> Subject: Re: 5.10 LTS Kernel: 2 or 6 years? Date: Thu, 18 Feb 2021 09:21:13 -0800 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <20210218165104.GC2013@sasha-vm> On 2/18/2021 8:51 AM, Sasha Levin wrote: > On Wed, Feb 17, 2021 at 11:48:21AM -0800, Scott Branden wrote: >> On 2021-02-17 1:40 a.m., Greg Kroah-Hartman wrote: >>> Following up on this as I did not hear back from you. Are you and/or >>> your company willing to help out with the testing of 5.10 to ensure that >>> it is a LTS kernel? So far I have not had any companies agree to help >>> out with this effort, which is sad to see as it seems that companies >>> want 6 years of stable kernels, yet do not seem to be able to at the >>> least, do a test-build/run of those kernels, which is quite odd... >> I personally cannot commit to supporting this kernel for 6 years >> (and personally do not want to backport new features to a 6 year old >> kernel). >> And customers are finicky and ask for one thing and then change their >> mind later. > > Why would we commit to maintining an upstream LTS for 6 years then? If > no one ends up using it (and we don't want anyone using older LTS > kernels) we're still stuck maintaining it. > >> We'll have to see what decisions are made at a company level for this >> as there >> are added costs to run tests on LTS kernel branches. We already run >> extensive QA on > > This sounds very wrong: it's ok to get volunteers to commit to 6 years > while the company that is asking for it won't do the same? > > Shouldn't Broadcom commit to the work involved here first? There are different groups within Broadcom, and Scott and I belong to different groups, so I can only speak for mine. We can talk about why I do not use the same email domain as Scott if you would like, and no, I cannot help you fix the Broadcom Wi-Fi drivers :) My group is committed to using the 5.10 kernel for the next 6 years because of Android TV and we will do our best to test the 5.10 stable RC as they come. We are a small team of 7 people in the grand scheme of our larger business activities, and we get pulled into way too many things, so we may skip testing a few stable releases once in a while. I do not know how to make it more official than that. As a company, we are most likely shooting ourselves in the foot by not having a point of coordination with the Linux Foundation and key people like you, Greg and other participants in the stable kernel. The usual left hand and right hand not having yet discovered each other, hey hi there left hand! I can see about remedying that at least for the interest of the group I work in. -- Florian
next prev parent reply other threads:[~2021-02-18 19:08 UTC|newest] Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-25 19:55 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 [this message] 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 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: 5.10 LTS Kernel: 2 or 6 years?' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).