From: Scott Wood <oss@buserror.net>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: natechancellor@gmail.com, ndesaulniers@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: Drop -me200 addition to build flags
Date: Mon, 16 Nov 2020 14:26:40 -0600 [thread overview]
Message-ID: <8b23cec8b7b490ec8ef578cbd2fe4316288d4e13.camel@buserror.net> (raw)
In-Reply-To: <20201116120913.165317-1-mpe@ellerman.id.au>
On Mon, 2020-11-16 at 23:09 +1100, Michael Ellerman wrote:
> Currently a build with CONFIG_E200=y will fail with:
>
> Error: invalid switch -me200
> Error: unrecognized option -me200
>
> Upstream binutils has never supported an -me200 option. Presumably it
> was supported at some point by either a fork or Freescale internal
> binutils.
>
> We can't support code that we can't even build test, so drop the
> addition of -me200 to the build flags, so we can at least build with
> CONFIG_E200=y.
>
> Reported-by: Németh Márton <nm127@freemail.hu>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> ---
>
> More discussion:
> https://lore.kernel.org/lkml/202011131146.g8dPLQDD-lkp@intel.com
> ---
> arch/powerpc/Makefile | 1 -
> 1 file changed, 1 deletion(-)
Acked-by: Scott Wood <oss@buserror.net>
I'd go further and remove E200 code entirely, unless someone with the hardware
can claim that it actually works. There doesn't appear to be any actual
platform support for an e200-based system. It seems to be a long-abandoned
work in progress.
-Scott
next prev parent reply other threads:[~2020-11-16 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 12:09 [PATCH] powerpc: Drop -me200 addition to build flags Michael Ellerman
2020-11-16 20:26 ` Scott Wood [this message]
2020-11-16 23:34 ` Nick Desaulniers
2020-11-17 23:15 ` Michael Ellerman
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=8b23cec8b7b490ec8ef578cbd2fe4316288d4e13.camel@buserror.net \
--to=oss@buserror.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
/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