linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Savochkin <saw@saw.sw.com.sg>
To: Christian Robottom Reis <kiko@async.com.br>
Cc: linux-kernel@vger.kernel.org, eepro100@scyld.com
Subject: Re: eepro100 problems with 2.2.19 _and_ 2.4.0
Date: Mon, 18 Jun 2001 15:41:34 -0400	[thread overview]
Message-ID: <20010618154134.A32175@saw.sw.com.sg> (raw)
In-Reply-To: <Pine.LNX.4.32.0106161923290.339-100000@blackjesus.async.com.br> <Pine.LNX.4.32.0106170037020.191-100000@blackjesus.async.com.br>
In-Reply-To: <Pine.LNX.4.32.0106170037020.191-100000@blackjesus.async.com.br>; from "Christian Robottom Reis" on Sun, Jun 17, 2001 at 12:40:34AM

On Sun, Jun 17, 2001 at 12:40:34AM -0300, Christian Robottom Reis wrote:
> 
> I am _very_ willing to devote some time to getting this fixed in both the
> kernel and Donald's drivers if anyone is interested in tracking down the
> problem. I'm not very familiar with the hardware, but I have a test box I
> can use freely, a bit of time spare, and I can reproduce the problem
> easily. I'd hate to see somebody else go through what I have just had to,
> so it would be nice to see this fixed or documented in an official-ese
> place.

I'm obviously interested in tracking it down.
I'll contact you with what we can test on you comp a couple of days later,
I'm quite busy right now, ok?

	Andrey

      reply	other threads:[~2001-06-18 19:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-17  2:26 eepro100 problems with 2.2.19 _and_ 2.4.0 Christian Robottom Reis
2001-06-17  2:43 ` Christian Robottom Reis
2001-06-17 15:49   ` Jeff Chua
2001-06-17 19:09     ` Christian Robottom Reis
2001-06-18  8:48       ` Jeff Chua
2001-06-17  3:40 ` Christian Robottom Reis
2001-06-18 19:41   ` Andrey Savochkin [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=20010618154134.A32175@saw.sw.com.sg \
    --to=saw@saw.sw.com.sg \
    --cc=eepro100@scyld.com \
    --cc=kiko@async.com.br \
    --cc=linux-kernel@vger.kernel.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 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).