From: Adam Borowski <kilobyte@angband.pl>
To: "Wadepohl, Wolfram" <wolfram.wadepohl@storopack.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: TLS for 5.10
Date: Mon, 8 Feb 2021 15:37:40 +0100 [thread overview]
Message-ID: <YCFMtITKsqgoahKT@angband.pl> (raw)
In-Reply-To: <9d7203defadd4cf3a1ae3f4a5f827ed3@stpinfexc1vp.corporate.storopack.net>
On Mon, Feb 08, 2021 at 07:08:05AM +0000, Wadepohl, Wolfram wrote:
> I'm sad to hear that 5.10 has still an EOL of Dec, 2022. We are in
> development of our 1st GNU/Linux based System, 50k devices for IoT.
[...]
> In general a 2 year support for embedded systems in automation is not a
> reasonable thing. Nevertheless the CIP project has commited to 5.10 as the
> next SLTS kernel.
[...]
> What can we do as a very small development team to support an extended LTS
> period of 5.10.?
The two years are a minimal promise from Greg. Debian is using 5.10 for
upcoming Bullseye, thus even if Greg won't extend (99% chance he will), Ben
Hutchings will continue the support for as long as Debian Bullseye is alive.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄⠀⠀⠀⠀ A master species delegates.
prev parent reply other threads:[~2021-02-08 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 7:08 TLS for 5.10 Wadepohl, Wolfram
2021-02-08 14:37 ` Adam Borowski [this message]
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=YCFMtITKsqgoahKT@angband.pl \
--to=kilobyte@angband.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=wolfram.wadepohl@storopack.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