From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux-Kernel list <linux-kernel@vger.kernel.org>, netdev@oss.sgi.com
Subject: Re: eepro100 (was Re: Linux 2.4.18-rc3)
Date: Thu, 21 Feb 2002 18:15:51 -0500 [thread overview]
Message-ID: <3C757FA7.BFD51A03@mandrakesoft.com> (raw)
In-Reply-To: <E16e2aJ-00007x-00@the-village.bc.nu>
Alan Cox wrote:
>
> > eepro100 users,
> >
> > If you can spare some time, please test and compare 2.4.17 and
> > 2.4.18-rc3 kernel versions, for (a) regressions in performance/behavior,
> > and (b) -fixed- or improved behavior.
>
> Just glancing over the code - shouldnt it use pci_enable device before
> checking the regions its assigned ?
>
> Also it seems to include linux/delay.h twice
indeed, thanks..
--
Jeff Garzik | XXX FREE! secure AFSPC AK-47 unclassified CDC
Building 1024 | NATO SAS CDMA fun with filters Bellcore kibo SSL
MandrakeSoft | high security goat clones infowar 2600 Magazine
prev parent reply other threads:[~2002-02-21 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 21:26 Linux 2.4.18-rc3 Marcelo Tosatti
2002-02-21 22:48 ` eepro100 (was Re: Linux 2.4.18-rc3) Jeff Garzik
2002-02-21 23:25 ` Alan Cox
2002-02-21 23:15 ` Jeff Garzik [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=3C757FA7.BFD51A03@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox