All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "SZ Lin (林上智)" <szlin@debian.org>
Cc: Alexander Sverdlin <alexander.sverdlin@gmail.com>,
	Lukasz Majewski <lukma@denx.de>,
	Ksummit-discuss@lists.linuxfoundation.org,
	Jonas Jensen <jonas.jensen@gmail.com>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Deprecation / Removal of old hardware support
Date: Fri, 28 Sep 2018 12:45:39 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1809281230180.2004@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20180927152512.GA3531@localhost>

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

On Thu, 27 Sep 2018, SZ Lin (林上智) wrote:

> > And this is good stuff, it's rock solid at this point. I just wish and
> > hope that they really invest in using the very latest kernels also for
> > these elder boards even though I rarely hear from them on the mailing
> > lists.
> 
> To have long-term maintenance kernel is very important for industrial application,
> that is why Moxa joined CIP [1].

That's not the question here. The question here is how do we keep old
hardware supported in the latest kernel and who makes sure that it is
supported.

CIP is trying to keep a dead kernel in zombie state for a very long time
and as recent events (the whole speculation mess) have shown this is not
really a sane approach because backporting of invasive security fixes is
anything between impossible, incomplete and outright dangerous.

So for events like Meltdown/Spectre/L1TF the right answer is to be able to
switch to a recent kernel on that old hardware, but that requires that the
old hardware is still properly supported.

That's what people are asking here: What to do with old hardware support in
the latest kernel. If it's just bitrotting because nobody cares, then we
rather remove it. If it should be kept supported, then someone has to step
up and make sure it is, manufacturer being the obvious candidate.

Thanks,

	tglx




  reply	other threads:[~2018-09-28 10:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10 14:04 [Ksummit-discuss] [MAINTAINERS SUMMIT] Deprecation / Removal of old hardware support Peter Huewe
2018-09-10 15:31 ` Linus Walleij
2018-09-10 21:40   ` Arnd Bergmann
2018-09-10 22:02     ` Guenter Roeck
2018-09-11  8:49       ` Geert Uytterhoeven
2018-09-11 17:27         ` Guenter Roeck
2018-09-11 17:58           ` Geert Uytterhoeven
2018-09-11 18:27             ` Guenter Roeck
2018-09-11 18:37               ` Daniel Vetter
2018-09-11  8:37     ` Linus Walleij
2018-09-11  9:37       ` Lukasz Majewski
2018-09-11 19:33         ` Greg KH
2018-09-11 21:39           ` Laurent Pinchart
2018-09-11 21:50             ` Thomas Gleixner
2018-09-12  6:40               ` Geert Uytterhoeven
2018-09-12 10:23                 ` Arnd Bergmann
2018-09-12  6:26             ` Greg KH
2018-09-12  6:49               ` Peter Huewe
2018-09-12  7:07                 ` Greg KH
2018-09-11 10:52       ` Mark Brown
2018-09-11 11:22         ` Linus Walleij
     [not found]           ` <TY2PR0101MB2526376DEFC241B754A19A6AE21C0@TY2PR0101MB2526.apcprd01.prod.exchangelabs.com>
2018-09-27 15:25             ` SZ Lin (林上智)
2018-09-28 10:45               ` Thomas Gleixner [this message]
2018-09-11 11:53       ` Arnd Bergmann
2018-09-11 21:28         ` Alexander Sverdlin
2018-09-11 21:16       ` Alexander Sverdlin

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=alpine.DEB.2.21.1809281230180.2004@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=Ksummit-discuss@lists.linuxfoundation.org \
    --cc=alexander.sverdlin@gmail.com \
    --cc=jonas.jensen@gmail.com \
    --cc=lukma@denx.de \
    --cc=szlin@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.