LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Michael Ellerman <email@example.com>
To: Jeremy Kerr <firstname.lastname@example.org>, Jonathan Corbet <email@example.com>,
Colin King <firstname.lastname@example.org>,
Geoff Levand <email@example.com>
Cc: David Airlie <firstname.lastname@example.org>,
Maarten Lankhorst <email@example.com>,
Maxime Ripard <firstname.lastname@example.org>,
Sean Paul <email@example.com>,
Subject: Re: [PATCH] Documentation: fix spelling mistake, EACCESS -> EACCES
Date: Mon, 12 Nov 2018 23:57:22 +1100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Jeremy Kerr <email@example.com> writes:
> Hi Jon,
>>> Signed-off-by: Colin Ian King <firstname.lastname@example.org>
>>> Documentation/filesystems/spufs.txt | 2 +-
>>> Documentation/gpu/drm-uapi.rst | 4 ++--
>>> 2 files changed, 3 insertions(+), 3 deletions(-)
>> Applied, thanks.
>> This is the first patch to spufs.txt since 2006...I wonder if that stuff
>> is being used by anybody...
> Anyone who is using the vector processors on the Cell BE processors will
> be using it. However, that hardware is becoming pretty rare now.
> We'll want to remove the spufs bits if/when we drop support for the cell
> platforms (IBM QSxx, PS3, celleb). mpe: any ides on that? Do you have a
> policy for dropping platform support?
I don't have a policy. We discussed it a bit at maintainer summit, that
basically boiled down to stuff should get removed when it is not used
much and/or is causing undue maintenance burden - both of which are
fairly arbitrary criteria.
My feeling is spufs is not causing anyone much work, it does get hit by
some VFS updates but it's just one of many many filesystems, so the
incremental overhead is pretty small I think - though VFS people may
I still have a working IBM QS22, and Geoff is still maintaining PS3,
celleb is gone.
Basically we're keeping it around in case people are still using it on
their PS3s. I don't know how we gauge how many people that is without
removing support and seeing who is annoyed. But even if we did that a
lot of folks will probably not notice for months to years, and when they
do notice they'll just bin their PS3s rather than telling us.
But maybe Geoff has a better feel for how many people (other than him)
are still running upstream on PS3s.
next prev parent reply other threads:[~2018-11-12 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 17:25 Colin King
2018-10-26 18:20 ` Miguel Ojeda
2018-10-26 18:40 ` Matthew Wilcox
2018-10-26 18:53 ` Miguel Ojeda
2018-10-26 18:54 ` Miguel Ojeda
2018-11-07 22:31 ` Jonathan Corbet
2018-11-08 0:38 ` Jeremy Kerr
2018-11-12 12:57 ` Michael Ellerman [this message]
2018-11-12 20:15 ` Geoff Levand
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: [PATCH] Documentation: fix spelling mistake, EACCESS -> EACCES' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).