From: Greg KH <gregkh@linuxfoundation.org>
To: Willy Tarreau <w@1wt.eu>
Cc: Theodore Ts'o <tytso@mit.edu>,
Michal Simek <michal.simek@amd.com>,
Kris Chaplin <kris.chaplin@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Reg the next LTS kernel (6.1?)
Date: Sat, 14 Jan 2023 09:26:07 +0100 [thread overview]
Message-ID: <Y8JnHyKNTHMjsHSb@kroah.com> (raw)
In-Reply-To: <20230114071412.GB5088@1wt.eu>
On Sat, Jan 14, 2023 at 08:14:12AM +0100, Willy Tarreau wrote:
> On Fri, Jan 13, 2023 at 04:40:19PM -0500, Theodore Ts'o wrote:
> > On Fri, Jan 13, 2023 at 05:22:56PM +0100, Greg KH wrote:
> > > > I am just saying that developers/driver owners can simple do calculation to
> > > > identify LTS version. When they know it they also know time when their
> > > > deadline is for upstreaming work. It means if patch is accepted between
> > > > 6.0-r1 and 6.0-rc5/6 they know that it will get to 6.1 merge window.
> > >
> > > That is what I am afraid of and if it causes problems I will purposfully
> > > pick the previous release. This has happened in the past and is never
> > > an excuse to get anything merged. Code gets merged when it is ready,
> > > not based on a LTS release.
> >
> > This is probably the best reason not to preannounce when the LTS
> > release will be ahead of time --- because it can be abused by
> > developers who try to get not-ready-for-prime-time features into what
> > they think will be the LTS kernel, with the result that the last
> > release of the year could be utterly unsitable for that perpose.
>
> We know this risk exists but since Greg never makes promises on any
> version, it remains reasonable.
I have to _not_ make promises because in the past when I did, people
threw crap into the kernel with the "justification" that they had to get
it in this specific kernel because it was going to be the LTS one.
We can't have nice things, because people abuse it :(
greg k-h
next prev parent reply other threads:[~2023-01-14 8:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 7:37 Reg the next LTS kernel (6.1?) Kaiwan N Billimoria
2022-10-07 7:46 ` Greg KH
2022-10-07 7:50 ` Kaiwan N Billimoria
2022-12-17 13:02 ` Kaiwan N Billimoria
2022-12-17 13:18 ` Greg KH
2022-12-17 13:44 ` Kaiwan N Billimoria
2022-12-17 16:40 ` Willy Tarreau
2022-12-20 1:45 ` Kaiwan N Billimoria
2022-12-18 8:42 ` Greg KH
2023-01-11 8:15 ` Conor Dooley
2023-01-11 11:33 ` Greg KH
2023-01-11 19:05 ` Conor Dooley
2023-01-12 12:23 ` Kris Chaplin
2023-01-12 12:26 ` Michal Simek
2023-01-13 11:27 ` Greg KH
2023-01-13 12:54 ` Michal Simek
2023-01-13 16:22 ` Greg KH
2023-01-13 21:40 ` Theodore Ts'o
2023-01-14 7:14 ` Willy Tarreau
2023-01-14 8:26 ` Greg KH [this message]
2023-01-14 8:47 ` Willy Tarreau
2023-02-05 6:27 ` Ruslan Bilovol
2023-02-16 10:41 ` Kris Chaplin
2023-02-16 11:20 ` Greg KH
2023-02-16 11:23 ` Kris Chaplin
2023-01-16 12:16 ` Michal Simek
2023-01-17 3:07 ` Theodore Ts'o
2023-01-16 12:02 ` Michal Simek
2023-01-13 11:24 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2022-10-07 15:04 Carl Dasantas
2022-10-07 15:36 ` Greg KH
2022-10-07 16:07 ` Carl Dasantas
2022-10-07 16:34 ` Greg KH
2022-10-07 19:50 ` Theodore Ts'o
2022-10-07 17:37 ` Slade Watkins
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=Y8JnHyKNTHMjsHSb@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kris.chaplin@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=tytso@mit.edu \
--cc=w@1wt.eu \
/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