From: "Grant Likely" <grant.likely@secretlab.ca>
To: "John Linn" <John.Linn@xilinx.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linuxppc-dev@ozlabs.org
Subject: Re: FW: [PATCH] Xilinx: BSP: Updated ML405 to match hardware used for testing
Date: Thu, 28 Feb 2008 09:17:50 -0700 [thread overview]
Message-ID: <fa686aa40802280817o1130e7feg1ebb381675c6e595@mail.gmail.com> (raw)
In-Reply-To: <20080228160718.4AA8E1298060@mail127-sin.bigfish.com>
On Thu, Feb 28, 2008 at 9:07 AM, John Linn <John.Linn@xilinx.com> wrote:
> I think I found my problem that mangled the messages. I really meant to
> send both messages to the embedded ppc list rather than this more
> general list.
Don't bother using linuxppc-embedded. Stick with linuxppc-dev. There
has been talk about merging the two lists.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
prev parent reply other threads:[~2008-02-28 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 23:15 FW: [PATCH] Xilinx: BSP: Updated ML405 to match hardware used for testing John Linn
2008-02-28 0:01 ` Stephen Rothwell
2008-02-28 16:07 ` John Linn
2008-02-28 16:17 ` Grant Likely [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=fa686aa40802280817o1130e7feg1ebb381675c6e595@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=John.Linn@xilinx.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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