LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.com>
To: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [RFC][PATCH 1/2] remove mpc83xx support from arch/ppc
Date: Tue, 03 Oct 2006 13:20:17 -0500	[thread overview]
Message-ID: <1159899616.14294.127.camel@cashmere.sps.mot.com> (raw)
In-Reply-To: <229C6ACA-4728-408B-9360-54249996E821@kernel.crashing.org>

On Thu, 2006-09-28 at 16:34, Kumar Gala wrote:
> On Sep 28, 2006, at 4:02 PM, Kim Phillips wrote:
> 
> > remove 83xx support from arch/ppc.  Tested multiple arch/defconfig  
> > build combinations ok.  AFAICT, everything 83xx works in arch/ 
> > powerpc, and new derivatives are being added only to arch/powerpc,  
> > so it's better not to keep this around.
> 
> NACK!! we need the cuImage stuff working and in the tree before I'm  
> ok with this.  We have to be able to boot from a non-flat-dev aware u- 
> boot before I'll be ok with removing 83xx from arch/ppc.
> 
> - kumar

Any idea when those patches are going to be in?

Thanks,
jdl

  reply	other threads:[~2006-10-03 18:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28 21:02 [RFC][PATCH 1/2] remove mpc83xx support from arch/ppc Kim Phillips
2006-09-28 21:34 ` Kumar Gala
2006-10-03 18:20   ` Jon Loeliger [this message]
2006-10-03 18:42     ` Kumar Gala

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=1159899616.14294.127.camel@cashmere.sps.mot.com \
    --to=jdl@freescale.com \
    --cc=linuxppc-dev@ozlabs.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