public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: "Kadel, Michael" <michael.kadel@karlstorz.com>
To: cip-dev@lists.cip-project.org
Subject: Re: projected EOL v4.4 SLTS
Date: Wed, 27 Sep 2023 00:28:19 -0700	[thread overview]
Message-ID: <29568.1695799699066068267@lists.cip-project.org> (raw)
In-Reply-To: <ed42752c-3a2e-4e47-9d48-f10b2c89da13@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 530 bytes --]

Hi Jan,

thanks for your fast answer.

I found this vague statement ".. *possibly 2036* " under: Linux kernel version history - Wikipedia ( https://en.wikipedia.org/wiki/Linux_kernel_version_history )

A use case:
End of Service for medical devices can vary from 5 to 10 years.
If the End of Life of a medical device was announced in 2018 or later, it runs out of support (e.g. cyber security patches for linux kernel v4.4)
This then leads to expensive alternative measures.

Again, thanks for clarification,
Michael

[-- Attachment #2: Type: text/html, Size: 615 bytes --]

  reply	other threads:[~2023-09-27  7:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22 14:10 projected EOL v4.4 SLTS Kadel, Michael
2023-09-26 13:53 ` Jan Kiszka
2023-09-27  7:28   ` Kadel, Michael [this message]
2023-09-28  6:52     ` Jan Kiszka
2023-10-02 11:59       ` Kadel, Michael
2023-10-03 20:26         ` Jan Kiszka

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=29568.1695799699066068267@lists.cip-project.org \
    --to=michael.kadel@karlstorz.com \
    --cc=cip-dev@lists.cip-project.org \
    /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