From: Jon Loeliger <jdl@freescale.com>
To: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Cc: Kumar Gala <galak@gate.crashing.org>
Subject: Re: [Fwd: [PATCH Repost] Add Uboot ASMP suport for MPC8641D]
Date: Wed, 21 Mar 2007 15:21:46 -0500 [thread overview]
Message-ID: <1174508506.6595.489.camel@ld0161-tx32> (raw)
In-Reply-To: <1174508310.6595.486.camel@ld0161-tx32>
On Wed, 2007-03-21 at 15:18, Jon Loeliger wrote:
> Kumar,
>
> As I indicated on IRC to you a few days ago, here is a copy
> of the Asymmetric Multi-Processor support patch for 8641 HPCN.
> For completeness and reference, the corresponding U-Boot patch
> will be posted to the U-Boot list as well.
>
> Thanks,
> jdl
>
> PS -- Apologies if this is a duplicate. The first appears
> to have dropped out of the ether into /dev/null.
Gah. This is the U-Boot patch!
I meant to send the Linux patch, of course!
Brown bag,
jdl
prev parent reply other threads:[~2007-03-21 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 20:18 [Fwd: [PATCH Repost] Add Uboot ASMP suport for MPC8641D] Jon Loeliger
2007-03-21 20:21 ` Jon Loeliger [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=1174508506.6595.489.camel@ld0161-tx32 \
--to=jdl@freescale.com \
--cc=galak@gate.crashing.org \
--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).