From: "Dale Farnsworth" <dale@farnsworth.org>
To: linuxppc-embedded@ozlabs.org
Subject: Re: linuxppc tree with mv64xxx included?
Date: Wed, 2 Mar 2005 13:35:20 -0700 [thread overview]
Message-ID: <20050302203520.GA12253@xyzzy> (raw)
In-Reply-To: <42260A4F.8030205@katalix.com>
On Wed, Mar 02, 2005 at 06:47:43PM +0000, James Chapman wrote:
> The latest ethernet code can be obtained from
> bk://farnsworth.bkbits.net/linux-2.5-mv643xx-enet
Make that bk://dfarnsworth@bkbits.net/linux-2.5-mv643xx-enet
-Dale
prev parent reply other threads:[~2005-03-02 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 1:23 linuxppc tree with mv64xxx included? Ron Bianco
2005-03-01 1:33 ` Mark A. Greer
2005-03-02 18:47 ` James Chapman
2005-03-02 19:03 ` Ron Bianco
2005-03-02 20:35 ` Dale Farnsworth [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=20050302203520.GA12253@xyzzy \
--to=dale@farnsworth.org \
--cc=linuxppc-embedded@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.