From: "Mark A. Greer" <mgreer@mvista.com>
To: mod+linuxppc-dev@MissionCriticalLinux.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: "broken" GT64260 ethernet driver
Date: Fri, 10 May 2002 13:30:41 -0400 [thread overview]
Message-ID: <3CDC03C1.DB7A0E49@mvista.com> (raw)
In-Reply-To: 200205101724.g4AHOaAD023769@odonnell.lowell.mclinux.com
mod+linuxppc-dev@MissionCriticalLinux.com wrote:
> > there have been a lot of "this driver is broken" comments
> > on the thread. I agree it's ugly, but it seems to work.
> > Can someone elaborate on exactly what is "broken"
>
> Last I knew, the situation was pretty much as you've described
> it: no profound problems (last I knew) and lots of griping.
Ditto.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-10 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200205100459.XAA27925@lists.linuxppc.org>
2002-05-10 17:13 ` "broken" GT64260 ethernet driver Bill Fincke
2002-05-10 17:24 ` mod+linuxppc-dev
2002-05-10 17:30 ` Mark A. Greer [this message]
2002-05-31 0:53 ` GT64260 ethernet driver - long term stability? Bill Fincke
2002-05-31 11:21 ` Geert Uytterhoeven
2002-05-31 21:52 ` Mark A. Greer
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=3CDC03C1.DB7A0E49@mvista.com \
--to=mgreer@mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mod+linuxppc-dev@MissionCriticalLinux.com \
/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.