linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Sasha Levin <sashal@kernel.org>,
	BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Scott Branden <scott.branden@broadcom.com>
Subject: Re: 5.10 LTS Kernel: 2 or 6 years?
Date: Thu, 18 Feb 2021 19:20:50 +0100	[thread overview]
Message-ID: <20210218182050.GB15217@1wt.eu> (raw)
In-Reply-To: <YC6ptKgsMh20tmu6@kroah.com>

On Thu, Feb 18, 2021 at 06:53:56PM +0100, Greg Kroah-Hartman wrote:
> On Thu, Feb 18, 2021 at 09:21:13AM -0800, Florian Fainelli wrote:
> > 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.
> 
> What does the LF have to do with this?
> 
> We are here, on the mailing lists, working with everyone.  Just test the
> -rc releases we make and let us know if they work or not for you, it's
> not a lot of "coordination" needed at all.
> 
> Otherwise, if no one is saying that they are going to need these for 6
> years and are willing to use it in their project (i.e. and test it),
> there's no need for us to maintain it for that long, right?

Greg, please remember I expressed I really need them for slightly more than
3 years (say 3.5-4) :-) I'm fine with helping a bit more as time permits if
this saves me from having to take over these kernels after you, like in the
past, but I cannot engage on the regularity of my availability.

Overall I think that a lot of people completely underestimate the amount
of work it requires to maintain stable kernels, and how much it could be
distributed. By having a bunch of users participate a little bit more
(e.g. by sometimes backporting the patches that are essential to them,
by testing what's relevant to their use case), it already offloads a lot
of work. I don't think the extra work requires to be much organized if
there are enough participants to share the efforts.

Regards,
Willy

  parent reply	other threads:[~2021-02-18 19:24 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 [this message]
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 \
    --in-reply-to=20210218182050.GB15217@1wt.eu \
    --to=w@1wt.eu \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=scott.branden@broadcom.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;
as well as URLs for NNTP newsgroup(s).