From: Arnd Bergmann <arnd@arndb.de>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/5] powerpc/40x: Add support for PowerPC 405EZ Acadia board
Date: Fri, 10 Oct 2008 18:16:55 +0200 [thread overview]
Message-ID: <200810101816.55399.arnd@arndb.de> (raw)
In-Reply-To: <20081010160522.GB13966@yoda.jdub.homelinux.org>
On Friday 10 October 2008, Josh Boyer wrote:
> It would, except for timing. =A0I didn't get a chance to convert
> 40x over before the merge window opened and I'd rather not try
> to cram it in during the 1 week we have. =A0And Acadia is ported
> now (and has been for a few weeks), so getting that in seemed
> to be an easier route to take.
>=20
> I do have plans to convert 40x for 2.6.29, and if there are
> major objections I can hold off Acadia until then. =A0I just
> don't like holding back board ports for the "next re-org".
>=20
How about just renaming 40x/acadia.c to 40x/ppc405_simple.c
without the merge? Then you can merge in the other platforms
as time permits and any other new ones can start using the
_simple platform right away.
Arnd <><
next prev parent reply other threads:[~2008-10-10 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 12:33 [PATCH 0/5] AMCC PowerPC 405EZ Acadia eval board port Josh Boyer
2008-10-09 12:56 ` [PATCH 3/5] powerpc/40x: Add AMCC PowerPC 405EZ to cputable Josh Boyer
2008-10-10 12:38 ` [PATCH 1/5] powerpc/40x: AMCC PowerPC 405EZ Acadia DTS Josh Boyer
2008-10-10 12:38 ` [PATCH 2/5] powerpc/40x: Add support for PowerPC 405EZ Acadia board Josh Boyer
2008-10-10 15:58 ` Arnd Bergmann
2008-10-10 16:05 ` Josh Boyer
2008-10-10 16:16 ` Arnd Bergmann [this message]
2008-10-10 17:08 ` Josh Boyer
2008-10-10 12:38 ` [PATCH 5/5] powerpc/40x: Add PowerPC 405EZ Acadia defconfig Josh Boyer
2008-10-10 12:38 ` [PATCH 4/5] powerpc/40x: Add cuboot wrapper for Acadia board 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=200810101816.55399.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=jwboyer@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).