public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Vergoz Michael <mvergoz@sysdoor.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 8139too.c patch for kernel 2.4.19
Date: Mon, 18 Nov 2002 04:05:33 -0500	[thread overview]
Message-ID: <3DD8AD5D.9010803@pobox.com> (raw)
In-Reply-To: <028901c28ead$10dfbd20$76405b51@romain>

Vergoz Michael wrote:

> Hi Jeff,
>
> What i see is the current driver _doesn't_ work on my realtek 8139C.
> With this one it work fine.


What does not work?  Does the driver load?  Can you ping?  Does the 
driver work for a little while then stop?  Does it work perfectly except 
under heavy load?

Also, please read "REPORTING-BUGS" file in a Linux kernel source tree 
for additional debugging information to provide (lspci, dmesg, etc.)

Your patch includes so much junk it is obviously unacceptable. 
Therefore, I request that you work with me (and other kernel developers) 
to narrow down the problem, so that it may be fixed.

Regards,

	Jeff




  parent reply	other threads:[~2002-11-18  8:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-18  2:49 8139too.c patch for kernel 2.4.19 Vergoz Michael
2002-11-18  7:34 ` Jeff Garzik
2002-11-18  8:50   ` Vergoz Michael
2002-11-18 17:04     ` Ducrot Bruno
2002-11-18  9:05 ` Jeff Garzik [this message]
2002-11-18 11:17   ` Andreas Steinmetz
2002-11-18 15:55 ` Jeff Garzik
2002-11-18 16:12   ` Andreas Steinmetz
2002-11-18 16:47 ` Jeff Garzik
2002-11-18 17:25 ` Jeff Garzik
2002-11-18 17:51   ` Vergoz Michael
2002-11-18 18:14 ` Jeff Garzik
2002-11-18 20:04   ` Vergoz Michael
2002-11-18 21:15 ` Jeff Garzik
2002-11-18 21:34 ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2002-11-18 17:15 Manfred Spraul

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=3DD8AD5D.9010803@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mvergoz@sysdoor.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