linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Zang Roy-r61911 <tie-fei.zang@freescale.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	Yang Xin-Xin-r48390 <Xin-Xin.Yang@freescale.com>,
	Paul Mackerras <paulus@samba.org>,
	Alexandre.Bounine@tundra.com
Subject: RE: [PATCH/2.6.17-rc4 1/10] Powerpc: Add general support for mpc7 448h pc2 (Taiga) platform
Date: Thu, 18 May 2006 20:35:52 +1000	[thread overview]
Message-ID: <1147948552.5192.9.camel@localhost.localdomain> (raw)
In-Reply-To: <9FCDBA58F226D911B202000BDBAD4673062C0A97@zch01exm40.ap.freescale.net>

On Thu, 2006-05-18 at 18:21 +0800, Zang Roy-r61911 wrote:
>  > On Thu, 2006-05-18 at 15:12 +0800, Zang Roy-r61911 wrote:
> > > > I'm not repeating Kumar's comments about that CONFIG_7xxx 
> > > > thing and that
> > > > 7xxx/ directory, it should all go.
> > > > 
> > > 
> > > Should I move my code to embedded6xx?
> > 
> > Probably for now yes.
> 
> I can migrate my code to embedded6xx technically. In fact, 
> I can move it into anywhere in the arch/powerpc/platforms. 
> While for mpc7448hpc2(taiga) board, it is not a embedded 
> application board. It is a high performance server! It seems
> odd to put code there :). What's your opinion?

I think we should do a platform/generic for boards that don't need more
than a single platform file, which I think will be the case once we are
done with your port ;)

Ben.

  reply	other threads:[~2006-05-18 10:36 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18 10:21 [PATCH/2.6.17-rc4 1/10] Powerpc: Add general support for mpc7 448h pc2 (Taiga) platform Zang Roy-r61911
2006-05-18 10:35 ` Benjamin Herrenschmidt [this message]
2006-05-18 10:39 ` Paul Mackerras
2006-05-18 14:06   ` Kumar Gala
2006-05-18 16:35 ` Kumar Gala
  -- strict thread matches above, loose matches on Subject: below --
2006-06-02  8:33 Liu Dave-r63238
2006-06-02  8:20 Zang Roy-r61911
2006-06-02 14:50 ` Kumar Gala
2006-06-03  0:36   ` Benjamin Herrenschmidt
2006-06-02  8:05 Zang Roy-r61911
2006-06-02  8:19 ` Benjamin Herrenschmidt
2006-06-02  7:40 Zang Roy-r61911
2006-06-02  7:38 Liu Dave-r63238
2006-06-02  8:17 ` Benjamin Herrenschmidt
2006-06-02  7:29 Zang Roy-r61911
2006-06-02  7:32 ` Benjamin Herrenschmidt
2006-05-26  6:49 Zang Roy-r61911
2006-05-26  7:34 ` Benjamin Herrenschmidt
2006-05-24  7:23 Zang Roy-r61911
2006-05-19  1:45 Zang Roy-r61911
2006-05-18 10:49 Zang Roy-r61911
2006-05-18  8:05 Zang Roy-r61911
2006-05-18 16:36 ` Kumar Gala
2006-05-18  7:12 Zang Roy-r61911
2006-05-18  7:22 ` Benjamin Herrenschmidt
2006-05-18 16:41   ` Kumar Gala
2006-05-18 22:04     ` Benjamin Herrenschmidt
2006-05-18 20:49   ` Andy Fleming
2006-05-26  6:05     ` Benjamin Herrenschmidt
2006-05-18  6:57 Zang Roy-r61911
2006-05-18  7:19 ` Benjamin Herrenschmidt
2006-05-18 16:43 ` Kumar Gala
2006-05-18  6:46 Zang Roy-r61911
2006-05-18  6:59 ` Benjamin Herrenschmidt
2006-05-18  4:12 Zang Roy-r61911

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=1147948552.5192.9.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=Alexandre.Bounine@tundra.com \
    --cc=Xin-Xin.Yang@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=tie-fei.zang@freescale.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).