public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ethan Weinstein <lists@stinkfoot.org>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: Hans-Peter Jansen <hpj@urpla.net>, linux-kernel@vger.kernel.org
Subject: Re: minor e1000 bug
Date: Tue, 23 Dec 2003 09:54:51 -0500	[thread overview]
Message-ID: <3FE8573B.2020209@stinkfoot.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0312231618590.28409-100000@localhost.localdomain>

Feldman, Scott wrote:
> On Mon, 22 Dec 2003, Ethan Weinstein wrote:
> 
> 
>>It'd be fantastic if we could get this implememted. I'm very pleased
>>with the quality of this driver save for this one small issue.  I'd be
>>glad to help test code if necessary as I have multiple systems using
>>e1000's, and several are testboxes.  It'd be nice to have some
>>semi-realtime stats from these cards.
> 
 >
> Ok, this is against 2.6.0, so you'll need to hand adjust it for other 
> kernels.  Let me know if you see any issues.
> 
> -scott


Much thanks. That seems to do it, tested lightly so far with two 
onboards (asus p4c800e, and supermicro X5DPL-IGM-0) using both kernels 
2.6.0 and 2.4.23, e1000-5.2.22, stats updates are much faster and seem 
more accurate. Will test with some PCI-X cards in the office tommorow, 
where I can really do some pounding.


-Ethan

  reply	other threads:[~2003-12-24  2:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C6F5CF431189FA4CBAEC9E7DD5441E0103424209@orsmsx402.jf.intel.com>
2003-12-24  0:29 ` minor e1000 bug Feldman, Scott
2003-12-23 14:54   ` Ethan Weinstein [this message]
2003-12-22 19:30 Feldman, Scott
2003-12-22 19:52 ` Ethan Weinstein
  -- strict thread matches above, loose matches on Subject: below --
2003-12-22  5:26 Feldman, Scott
2003-12-22 10:26 ` Hans-Peter Jansen
2003-12-22 15:26 ` Ethan Weinstein
2003-12-19 20:40 Ethan Weinstein
2003-12-20 12:46 ` Hans-Peter Jansen

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=3FE8573B.2020209@stinkfoot.org \
    --to=lists@stinkfoot.org \
    --cc=hpj@urpla.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scott.feldman@intel.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