LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Geoff Levand <geoff@infradead.org>
To: Michael Ellerman <mpe@ellerman.id.au>,
	Jeremy Kerr <jk@ozlabs.org>, Jonathan Corbet <corbet@lwn.net>,
	Colin King <colin.king@canonical.com>
Cc: David Airlie <airlied@linux.ie>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	Sean Paul <sean@poorly.run>,
	linuxppc-dev@lists.ozlabs.org, linux-doc@vger.kernel.org,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: fix spelling mistake, EACCESS -> EACCES
Date: Mon, 12 Nov 2018 12:15:27 -0800	[thread overview]
Message-ID: <84e64a8b-765b-e89d-7427-5fd3a660575f@infradead.org> (raw)
In-Reply-To: <87bm6ua1xp.fsf@concordia.ellerman.id.au>

Hi Everyone,

On 11/12/2018 04:57 AM, Michael Ellerman wrote:
> But maybe Geoff has a better feel for how many people (other than him)
> are still running upstream on PS3s.

There are still PS3 users out there.  They are hobbyists who
generally don't post to Linux kernel mailing lists.  I usually
get one or two mail or IRC inquiries every month, many asking
how to get a recent kernel running.

I try keep my dev repo at k.org up to the latest -rc release
and tested on the retail PS3.  For more info see:

  https://git.kernel.org/pub/scm/linux/kernel/git/geoff/ps3-linux.git
  https://www.kernel.org/pub/linux/kernel/people/geoff/cell/README

-Geoff

      reply	other threads:[~2018-11-12 20:15 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
2018-11-12 20:15       ` Geoff Levand [this message]

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=84e64a8b-765b-e89d-7427-5fd3a660575f@infradead.org \
    --to=geoff@infradead.org \
    --cc=airlied@linux.ie \
    --cc=colin.king@canonical.com \
    --cc=corbet@lwn.net \
    --cc=jk@ozlabs.org \
    --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=mpe@ellerman.id.au \
    --cc=sean@poorly.run \
    --subject='Re: [PATCH] Documentation: fix spelling mistake, EACCESS -> EACCES' \
    /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

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).