From: Josh Boyer <jwboyer@jdub.homelinux.org>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: ARCH=ppc vs ARCH=powerpc
Date: Sun, 08 Jul 2007 22:38:28 -0500 [thread overview]
Message-ID: <1183952308.3308.2.camel@vader.jdub.homelinux.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0707061706140.4792@mtfhpc.demon.co.uk>
On Fri, 2007-07-06 at 17:21 +0100, Mark Fortescue wrote:
> Hi,
>
> I have noticed and read a few comments regarding the demise of ARCH=ppc.
>
> Having two PowerPC arcitectures and only supprting one of them makes
> little sense. Is it not time to migrate (where required) the remaining
> code from arch/ppc to arch/powerpc and asm-ppc to asm-powerpc. There are
> not many files left that are unique to ARCH=ppc so it should not take too
> long.
It was started in 2005. It's taken too long already.
Bug fixes will still be taken until arch/ppc dies. New platform/board
support, no.
josh
prev parent reply other threads:[~2007-07-09 3:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 16:21 ARCH=ppc vs ARCH=powerpc Mark Fortescue
2007-07-09 0:34 ` Arnd Bergmann
2007-07-09 3:37 ` Josh Boyer
2007-07-09 14:33 ` Mark Fortescue
2007-07-09 3:38 ` Josh Boyer [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=1183952308.3308.2.camel@vader.jdub.homelinux.org \
--to=jwboyer@jdub.homelinux.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mark@mtfhpc.demon.co.uk \
/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