From: Lukasz Majewski <lukma@denx.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Wolfgang Denk <wd@denx.de>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [thud][PATCH] ppce500v2: remove spe *The PowerPC SPE support is split off to a separate powerpcspe port
Date: Fri, 16 Nov 2018 13:31:24 +0100 [thread overview]
Message-ID: <20181116133124.14279e76@jawa> (raw)
In-Reply-To: <6338fea41b758f901b90c9d378c50e824fb01593.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
Hi Richard,
> What does "The PowerPC SPE support is split off to a separate
> powerpcspe port" mean?
>
> That gcc support is being dropped and its going somewhere separate?
>
> That we're dropping spe support from OE?
I do hope NOT.
There are still some users of those SPE SoCs. Please do not remove it
from OE.
>
> Cheers,
>
> Richard
>
>
>
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 499 bytes --]
next prev parent reply other threads:[~2018-11-16 12:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 3:40 [thud][PATCH] ppce500v2: remove spe *The PowerPC SPE support is split off to a separate powerpcspe port C.r. Guo
2018-11-16 11:54 ` Richard Purdie
2018-11-16 12:31 ` Lukasz Majewski [this message]
2018-11-16 12:45 ` richard.purdie
2018-11-19 9:56 ` C.r. Guo
2018-11-19 10:23 ` Lukasz Majewski
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=20181116133124.14279e76@jawa \
--to=lukma@denx.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=wd@denx.de \
/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