From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Jeff Garzik <jgarzik@pobox.com>, David Acker <dacker@roinet.com>
Cc: Bill Davidsen <davidsen@tmr.com>, Adrian Bunk <bunk@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
saw@saw.sw.com.sg
Subject: Re: [2.6.25 patch] the planned eepro100 removal
Date: Thu, 25 Oct 2007 15:43:20 -0700 [thread overview]
Message-ID: <47211C08.2040601@intel.com> (raw)
In-Reply-To: <47211A67.2090201@pobox.com>
Jeff Garzik wrote:
> Bill Davidsen wrote:
>> Adrian Bunk wrote:
>>> This patch contains the planned removal of the eepro100 driver.
>>>
>> Are the e100 people satisfied that e100 now handles all known cases? I
>
> Nope. There are still e100 work outstanding that means we cannot kill
> eepro100.
Agreed, there is still a receive unit hang in the last version that I got from
David Acker.
Auke
next prev parent reply other threads:[~2007-10-25 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 16:24 [2.6.25 patch] the planned eepro100 removal Adrian Bunk
2007-10-25 20:42 ` Bill Davidsen
2007-10-25 22:36 ` Jeff Garzik
2007-10-25 22:43 ` Kok, Auke [this message]
2007-10-26 13:42 ` David Acker
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=47211C08.2040601@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=bunk@kernel.org \
--cc=dacker@roinet.com \
--cc=davidsen@tmr.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
/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).