From: Dan Malek <dan@embeddededge.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-embedded@lists.linuxppc.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Organisation of 4xx initialization code
Date: Fri, 16 Nov 2001 20:11:40 -0500 [thread overview]
Message-ID: <3BF5B94C.2000404@embeddededge.com> (raw)
In-Reply-To: 20011117114724.H12763@zax
David Gibson wrote:
> .......... create a new ppc4xx.c which
> will probably have a lot of code copied out of ppc4xx_setup.c,
Oh great, even more new files names......
> Gradually move each of the other 4xx machines over to the new scheme
> and finally remove ppc4xx_setup.c
How about you just do them all at once so we don't have a mess with
some old and some new methods? Even if you can't test the changes,
contact someone that can and offer to do the best at changes. Nothing
is worse than making major changes to only some of the files, leaving
someone else to do the remainder when they are busy trying to accomplish
something else.
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-17 1:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 5:46 Organisation of 4xx initialization code David Gibson
2001-11-16 11:57 ` Matt Porter
2001-11-16 15:51 ` Tom Rini
2001-11-16 16:42 ` Matt Porter
2001-11-16 17:13 ` Tom Rini
2001-11-16 23:24 ` Dan Malek
2001-11-17 0:43 ` David Gibson
2001-11-17 1:01 ` Dan Malek
2001-11-17 2:18 ` Tom Rini
2001-11-17 11:16 ` Paul Mackerras
2001-11-17 12:43 ` Ralph Blach
2001-11-17 14:46 ` Mark Pilon
2001-11-17 0:50 ` David Gibson
2001-11-17 2:16 ` Tom Rini
2001-11-17 0:35 ` David Gibson
2001-11-17 2:18 ` Tom Rini
2001-11-16 16:07 ` Mark Pilon
2001-11-16 17:29 ` Tom Rini
2001-11-16 14:59 ` Tom Rini
2001-11-17 0:40 ` David Gibson
2001-11-17 2:15 ` Tom Rini
2001-11-16 16:46 ` Dan Malek
2001-11-17 0:47 ` David Gibson
2001-11-17 1:11 ` Dan Malek [this message]
2001-11-16 17:15 ` Armin Kuster
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=3BF5B94C.2000404@embeddededge.com \
--to=dan@embeddededge.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=paulus@samba.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).