From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Josh Boyer" <jwboyer@gmail.com>
Cc: linuxppc-dev@ozlabs.org, Adrian Bunk <bunk@kernel.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: 4xx support in arch/ppc is going away Real Soon Now
Date: Fri, 6 Jun 2008 08:53:18 -0600 [thread overview]
Message-ID: <fa686aa40806060753i76b1d652ldd2bb99f5406dab@mail.gmail.com> (raw)
In-Reply-To: <20080606085601.623ef866@vader.jdub.homelinux.org>
On Fri, Jun 6, 2008 at 7:56 AM, Josh Boyer <jwboyer@gmail.com> wrote:
> On Fri, 6 Jun 2008 14:53:47 +0300
> Adrian Bunk <bunk@kernel.org> wrote:
>
>> On Thu, Jun 05, 2008 at 09:11:48AM -0600, Grant Likely wrote:
>> > On Thu, Jun 5, 2008 at 8:52 AM, Josh Boyer <jwboyer@linux.vnet.ibm.com> wrote:
>> > > This commit (patch omitted due to size) is sitting in my local tree:
>> > >
>> > > commit 0d7efc1e80fc262bcc507a605482c5681e3f082a
>> > > Author: Josh Boyer <jwboyer@linux.vnet.ibm.com>
>> > > Date: Thu Jun 5 09:46:17 2008 -0500
>> > >
>> > > ppc/4xx: Remove 4xx support from arch/ppc
>> > >
>> > > Remove support for PPC 403, 405, and 440 processors from arch/ppc. The
>> > > arch/powerpc equivalents should be used. Boards that are not ported yet
>> > > will need to be ported to arch/powerpc to have continued support.
>> >
>> > This looks like unneeded churn.
>> >
>> > Paulus, Can we just kill all of arch/ppc for .27 right now?
>>
>> Is anyone already working on doing this and the cleanups that will then
>> be possible?
>>
>> Otherwise I'll be glad to contribute to it. :)
>
> I think we can handle it. Thanks though.
BTW Paul, we agreed in your absence on IRC that you should take the
honors of committing the kill arch/ppc patch and the associated top
spot in LWN's top committers list... but there's a price. You may
very well get mailed the bar tab from the ding-dong-arch-ppc-is-dead
party at OLS this year. >:-}
Oh, and we're going try to create the longest acked-by chain in Linux history.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-06-06 14:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 14:52 4xx support in arch/ppc is going away Real Soon Now Josh Boyer
2008-06-05 15:11 ` Grant Likely
2008-06-05 15:18 ` Josh Boyer
2008-06-05 15:48 ` Stephen Neuendorffer
2008-06-05 20:12 ` Arnd Bergmann
2008-06-05 20:27 ` Grant Likely
2008-06-05 20:28 ` Olof Johansson
2008-06-05 20:30 ` Scott Wood
2008-06-05 20:37 ` Becky Bruce
2008-06-06 11:19 ` Wolfgang Denk
2008-06-06 15:34 ` Jon Loeliger
2008-06-06 21:11 ` Sean MacLennan
2008-06-07 7:36 ` Peter Korsgaard
2008-06-07 10:07 ` Stefan Roese
2008-06-08 14:57 ` Jochen Friedrich
2008-06-08 16:15 ` Adrian Bunk
2008-06-05 20:40 ` Segher Boessenkool
2008-06-06 4:32 ` Benjamin Herrenschmidt
2008-06-06 4:38 ` Kumar Gala
2008-06-06 8:39 ` Stefan Roese
2008-06-05 18:59 ` 4xx support in " Kumar Gala
2008-06-05 19:13 ` Josh Boyer
2008-06-06 11:53 ` Adrian Bunk
2008-06-06 12:09 ` Paul Mackerras
2008-06-06 17:58 ` Adrian Bunk
2008-06-06 13:56 ` Josh Boyer
2008-06-06 14:53 ` Grant Likely [this message]
2008-06-07 12:09 ` Paul Mackerras
2008-06-08 15:54 ` Jon Loeliger
2008-06-09 7:46 ` Geert Uytterhoeven
2008-06-09 16:21 ` John Linn
2008-06-11 21:31 ` Vitaly Bordug
2008-06-16 14:10 ` Matthias Fuchs
2008-06-16 18:05 ` Josh Boyer
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=fa686aa40806060753i76b1d652ldd2bb99f5406dab@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=bunk@kernel.org \
--cc=jwboyer@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
/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).