From: Linus Walleij <linus.walleij@linaro.org>
To: Peter Huewe <PeterHuewe@gmx.de>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Deprecation / Removal of old hardware support
Date: Mon, 10 Sep 2018 17:31:37 +0200 [thread overview]
Message-ID: <CACRpkdYk1JKEQ=bumrxRk1eJ97xkQti8E1MRJ_xxen+dZ1a1Xw@mail.gmail.com> (raw)
In-Reply-To: <trinity-b7dcc7ee-84eb-4ba9-ab94-b2936551a388-1536588284133@3c-app-gmx-bs33>
On Mon, Sep 10, 2018 at 4:04 PM Peter Huewe <PeterHuewe@gmx.de> wrote:
> one topic I would like to discuss is: when is it time to remove support for old hardware?
> Should we support as much hardware as possible forever, or does it make sense to cut down the support?
> If so, when would be appropriate?
I've been thinking a lot about it. I just recently prepared a talk on the
subject.
My thinking has been something along the lines: if it has active
users we don't delete it, by the same token that we don't destroy
kernel interfaces that have active users.
Of course the definition of "users" is a bit complex there. In our
opinion the "users" are those who regularly compile new kernels
and test them, finds regressions, bisects problems and generally
do a good job in the community. Not ranting bloggers.
By this reasoning it is absolutely forbidden to propose something
like to delete arch/m68k (the last CPU M68060 produced in
1994 IIUC) as long as these maintainers put in an honest effort to
keep running that kernel on increasingly aging and hard to obtain
hardware like Apollo/Domain or Amiga 4000.
One day the last m68k users stops responding to regressions and
then it can be deleted.
My ARMv4 is another example, but I can point at new devices
beging deployed as we speak, using that ISA, even though it is
from 1999. So it has many active users (and maintainers).
(CC:ing the m68k maintainer, who is an awesome guy.)
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-09-10 15:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 14:04 Peter Huewe
2018-09-10 15:31 ` Linus Walleij [this message]
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
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='CACRpkdYk1JKEQ=bumrxRk1eJ97xkQti8E1MRJ_xxen+dZ1a1Xw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=Ksummit-discuss@lists.linuxfoundation.org \
--cc=PeterHuewe@gmx.de \
--cc=geert@linux-m68k.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