From: Jeremy Kerr <jk@ozlabs.org>
To: Jonathan Corbet <corbet@lwn.net>, Colin King <colin.king@canonical.com>
Cc: kernel-janitors@vger.kernel.org, linux-doc@vger.kernel.org,
David Airlie <airlied@linux.ie>,
linuxppc-dev@lists.ozlabs.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
linux-kernel@vger.kernel.org,
Michael Ellerman <michael@ellerman.id.au>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Sean Paul <sean@poorly.run>
Subject: Re: [PATCH] Documentation: fix spelling mistake, EACCESS -> EACCES
Date: Thu, 8 Nov 2018 08:38:15 +0800 [thread overview]
Message-ID: <d1048515-239a-2686-e897-fb2a2b8d180f@ozlabs.org> (raw)
In-Reply-To: <20181107153104.71eddf4d@lwn.net>
Hi Jon,
>> Signed-off-by: Colin Ian King <colin.king@canonical.com>
>> ---
>> 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?
Cheers,
Jeremy
next prev parent reply other threads:[~2018-11-08 0:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 17:25 [PATCH] Documentation: fix spelling mistake, EACCESS -> EACCES 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 [this message]
2018-11-12 12:57 ` Michael Ellerman
2018-11-12 20:15 ` Geoff Levand
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=d1048515-239a-2686-e897-fb2a2b8d180f@ozlabs.org \
--to=jk@ozlabs.org \
--cc=airlied@linux.ie \
--cc=colin.king@canonical.com \
--cc=corbet@lwn.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime.ripard@bootlin.com \
--cc=michael@ellerman.id.au \
--cc=sean@poorly.run \
/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;
as well as URLs for NNTP newsgroup(s).