From: Dan Malek <dan@embeddededge.com>
To: "Curtis,
Allen (by way of Allen Curtis <acurtis@onz.com>)"
<Allen.Curtis@Thales-IFS.com>
Cc: PPC Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: MPC8266ADS patch
Date: Wed, 10 Sep 2003 23:44:32 -0400 [thread overview]
Message-ID: <3F5FEFA0.1080809@embeddededge.com> (raw)
In-Reply-To: 5.2.1.1.2.20030910174452.02767580@192.168.1.10
Curtis, Allen (by way of Allen Curtis ) wrote:
> Here is a patch to make MPC8266ADS its own platform. Instead of creating a
> new platforms/ads8266.h header, ....
Will the "other issues to be addressed" cause the need for more definitions
or further #ifdefs in the existing file? If so, let's just go ahead and
create the new file now and just add to it later.
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-11 3:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 0:50 MPC8266ADS patch Curtis, Allen
2003-09-11 3:44 ` Dan Malek [this message]
2003-09-11 7:18 ` Rakesh Jagota
2003-09-11 7:44 ` PPC 405 Rakesh Jagota
2003-09-11 13:37 ` Andrew H Pham
2003-09-12 5:11 ` Rakesh Jagota
2003-09-12 15:50 ` MPC8266ADS patch Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2003-09-12 15:59 Curtis, Allen
2003-09-12 16:17 ` Tom Rini
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=3F5FEFA0.1080809@embeddededge.com \
--to=dan@embeddededge.com \
--cc=Allen.Curtis@Thales-IFS.com \
--cc=linuxppc-embedded@lists.linuxppc.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).