From: Kumar Gala <kumar.gala@freescale.com>
To: "Marcelo Tosatti" <marcelo.tosatti@cyclades.com>
Cc: "Nei A. Chiaradia" <nei.chiaradia@cyclades.com>,
linuxppc-embedded <linuxppc-embedded@ozlabs.org>,
Wanda Rosalino <wanda.rosalino@cyclades.com>,
Regina Kodato <regina.kodato@cyclades.com>
Subject: Re: [PATCH] PRxK sub-architecture
Date: Fri, 15 Oct 2004 16:13:10 -0500 [thread overview]
Message-ID: <04442B50-1EEF-11D9-BAB6-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <20041015165538.GB4131@logos.cnet>
(realized after the fact that this belonged on linuxppc-embedded)
A few comments:
1. Any reason for the duplicated header between include/asm-ppc/prxk.h
& arch/ppc/platforms/prxk.h?
2. Does flash.h really belong in include/asm-ppc?
- kumar
[snip]
prev parent reply other threads:[~2004-10-15 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 16:09 [PATCH] PRxK sub-architecture Marcelo Tosatti
2004-10-15 18:15 ` Tom Rini
2004-10-15 16:55 ` Marcelo Tosatti
2004-10-15 21:13 ` Kumar Gala [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=04442B50-1EEF-11D9-BAB6-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=nei.chiaradia@cyclades.com \
--cc=regina.kodato@cyclades.com \
--cc=wanda.rosalino@cyclades.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).