linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom.gr>
To: Florian Schirmer <jolt@tuxbox.org>
Cc: dan@embeddededge.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.5 on MPC823
Date: Thu, 05 Jun 2003 10:52:58 +0300	[thread overview]
Message-ID: <3EDEF6DA.2060001@intracom.gr> (raw)
In-Reply-To: <000101c32b36$ac2bb600$0100a8c0@space.taytron.net>


Florian Schirmer wrote:

>Hi,
>
>Dan, any news on 2.5 && MPC823? I know you where working on it. Did you
>manage to get arch/ppc/kernel/head_8xx.S thing up an running?
>
>Thanks,
>   Florian
>
>
>
>
>
>
Let me second that.

Regards

Pantelis


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-06-05  7:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05  7:47 2.5 on MPC823 Florian Schirmer
2003-06-05  7:52 ` Pantelis Antoniou [this message]
2003-06-05 15:46   ` Dan Malek
2003-06-12  6:27     ` Florian Schirmer

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=3EDEF6DA.2060001@intracom.gr \
    --to=panto@intracom.gr \
    --cc=dan@embeddededge.com \
    --cc=jolt@tuxbox.org \
    --cc=linuxppc-dev@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).