From: Dan Malek <dan@mvista.com>
To: andrew may <acmay@acmay.homeip.net>
Cc: John Tyner <jtyner@cs.ucr.edu>,
linuxppc-commit@source.mvista.com,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: ppc405 enet changes (fwd)
Date: Tue, 04 Sep 2001 20:06:26 -0400 [thread overview]
Message-ID: <3B956C82.D2D7E9C6@mvista.com> (raw)
In-Reply-To: 20010904152608.B14548@ecam.san.rr.com
andrew may wrote:
> Well we don't have the hardware to do multiple devices. I just know
> that is possible in the future. I would prefer to go through the
> pain of removing the static's now rather than later.
Ummm...OK, I guess.
> No I don't expect the patch to go in quickly. I just wanted John
> to start the process off.
OK. Once I actually get the 2_4_devel kernel booting and running with
some sense of reliability, I'll add the patch and give it a go.
> So if you want to point to specific code that you don't like let
> us know.
Yeah, all of the linux version stuff. It is nice to get patches against
the current 2_4 or 2_4_devel that are known to be tested and working.
If you can't test it, don't expect a quick turn around because someone
else (like me :-) has to spend the time doing it.
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-05 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.30.0109031513110.21186-200000@hill.cs.ucr.edu>
[not found] ` <20010903202915.A25163@cpe-24-221-152-185.az.sprintbbd.net>
2001-09-04 20:07 ` ppc405 enet changes (fwd) andrew may
[not found] ` <3B9557CA.D76C70E2@mvista.com>
2001-09-04 22:26 ` andrew may
2001-09-05 0:06 ` Dan Malek [this message]
[not found] ` <20010904180915.E14548@ecam.san.rr.com>
2001-09-05 2:39 ` Tom Rini
[not found] ` <3B9632EB.51904875@mvista.com>
2001-09-05 16:09 ` acmay
2001-09-05 16:25 ` acmay
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=3B956C82.D2D7E9C6@mvista.com \
--to=dan@mvista.com \
--cc=acmay@acmay.homeip.net \
--cc=jtyner@cs.ucr.edu \
--cc=linuxppc-commit@source.mvista.com \
--cc=linuxppc-embedded@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 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.