From: Kumar Gala <galak@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: [CURIOUSITY] When will we stop caring about arch/ppc?
Date: Mon, 25 Jun 2007 14:42:13 -0500 [thread overview]
Message-ID: <0FBD8D7C-1A60-4305-992C-5C28ECE41278@kernel.crashing.org> (raw)
In-Reply-To: <1182796800.23775.51.camel@weaponx.rchland.ibm.com>
On Jun 25, 2007, at 1:40 PM, Josh Boyer wrote:
> On Mon, 2007-06-25 at 11:23 -0700, Mark A. Greer wrote:
>> Any opinions on when we stop worrying about arch/ppc and start
>> getting
>> rid of it for real?
>
> There are lots of boards in the 4xx family that don't exist yet in
> powerpc. I don't think we want it to die until they get moved
> over, or
> at least marked as in a "danger zone" for a while.
Agreed, we need to go through and figure out what all really needs to
get moved over for other boards. I know 4xx has only one board
supported in arch/powerpc and I dont believe the support is complete.
> Maybe what we could do is designate a kernel release where we'll stop
> taking new arch/ppc submissions?
I think we stopped taking new submissions to arch/ppc a while ago...
someone sneak something in on us? We tend to only do bug fixes or
deal with issues related to moving things between arch/ppc & arch/
powerpc.
- k
next prev parent reply other threads:[~2007-06-25 19:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 18:23 [CURIOUSITY] When will we stop caring about arch/ppc? Mark A. Greer
2007-06-25 18:40 ` Josh Boyer
2007-06-25 19:42 ` Kumar Gala [this message]
2007-06-25 20:50 ` Josh Boyer
2007-06-26 7:48 ` Segher Boessenkool
2007-06-26 13:32 ` Josh Boyer
2007-06-26 13:46 ` Segher Boessenkool
2007-06-26 13:57 ` Josh Boyer
2007-06-26 17:03 ` Arnd Bergmann
2007-06-26 18:51 ` Kumar Gala
2007-06-26 21:11 ` Vitaly Bordug
2007-06-26 17:18 ` Mark A. Greer
2007-07-03 18:29 ` Scott Wood
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=0FBD8D7C-1A60-4305-992C-5C28ECE41278@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=Linuxppc-dev@ozlabs.org \
--cc=jwboyer@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).