From: Jeremy Kerr <jk@ozlabs.org>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: cbe-oss-dev@ozlabs.org, Arnd Bergmann <arnd@arndb.de>, dja@axtens.net
Subject: Re: [PATCH] powerpc: Remove the celleb support
Date: Wed, 01 Apr 2015 15:15:54 +0800 [thread overview]
Message-ID: <551B9B2A.10109@ozlabs.org> (raw)
In-Reply-To: <1426738520-21905-1-git-send-email-mpe@ellerman.id.au>
Hi Michael,
> The celleb code has seen no actual development for ~7 years.
>
> We (maintainers) have no access to test hardware, and it is highly
> likely the code has bit-rotted.
>
> As far as we're aware the hardware was never widely available, and is
> certainly no longer available, and no one on the list has shown any
> interest in it over the years.
>
> So remove it. If anyone has one and cares please speak up.
I've never had any spufs-related feedback from celleb platforms either.
Acked-by: Jeremy Kerr <jk@ozlabs.org>
Cheers,
Jeremy
prev parent reply other threads:[~2015-04-01 7:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 4:15 [PATCH] powerpc: Remove the celleb support Michael Ellerman
2015-03-25 5:25 ` Benjamin Herrenschmidt
2015-04-01 7:15 ` Jeremy Kerr [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=551B9B2A.10109@ozlabs.org \
--to=jk@ozlabs.org \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=dja@axtens.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).