From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org
Subject: Re: PATCH powerpc: 00/04 Remove __pmac, etc, sections, merge sections.h
Date: Mon, 19 Sep 2005 08:13:16 +1000 [thread overview]
Message-ID: <1127081596.4502.8.camel@gaston> (raw)
In-Reply-To: <216D7B09-CC72-482D-9C06-3416D5E02DBE@freescale.com>
> I think the discussion earlier in this week lead us to believe this
> was the way to go. We can provide a simple patch to allow selecting
> CHRP/PMAC/PREP specifically in addition to MUTLIPLATFORM.
It should be done like ppc64, that is MULTIPLATFORM can be built with an
aribtrary "set" of platforms. In fact, I think the merged arch should
trash if possible all "exclusive" CONFIG_MYBOARD stuff, but only ever do
what ppc64 does, that is any combination of platforms for the same CPU
family can be built at the same time.
Ben.
prev parent reply other threads:[~2005-09-18 22:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 15:31 PATCH powerpc: 00/04 Remove __pmac, etc, sections, merge sections.h Jon Loeliger
2005-09-17 15:35 ` PATCH powerpc: 01/04 Remove sections use from ppc Jon Loeliger
2005-09-17 15:36 ` PATCH powerpc: 02/04 Remove sections use from ppc64 and drivers Jon Loeliger
2005-09-17 15:38 ` PATCH powerpc: 03/04 Remove section free() and linker script bits Jon Loeliger
2005-09-17 15:39 ` PATCH powerpc: 04/04 Merge simplified sections.h into asm-powerpc Jon Loeliger
2005-09-18 1:25 ` PATCH powerpc: 00/04 Remove __pmac, etc, sections, merge sections.h Benjamin Herrenschmidt
2005-09-18 17:50 ` Kumar Gala
2005-09-18 22:13 ` Benjamin Herrenschmidt [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=1127081596.4502.8.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-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;
as well as URLs for NNTP newsgroup(s).