From: Manfred Spraul <manfred@colorfullife.com>
To: Vergoz Michael <mvergoz@sysdoor.com>
Cc: linux-kernel@vger.kernel.org, jgarzik@pobox.com
Subject: Re: 8139too.c patch for kernel 2.4.19
Date: Mon, 18 Nov 2002 18:15:18 +0100 [thread overview]
Message-ID: <3DD92026.3020506@colorfullife.com> (raw)
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 you have send to the list is a huge change:
ShuChen Shao took the 0.9.15 driver and added 8139 C+ support to it. This will not go into the kernel, instead the kernel contains a new driver for the 8139C+ nic.
You took his driver and added additional changes to it.
Meanwile development continued in the kernel driver [version 0.9.25].
Now we must try to merge everything again. Unfortunately this means manually figuring out which of your changes are required and which back out bugfixes.
Could you try to shrink your patch down to the necessary changes?
- did the 8139c+ driver from ShuChen work?
- create a diff with just your changes.
And add some description about your problem.
--
Manfred
next reply other threads:[~2002-11-18 17:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 17:15 Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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=3DD92026.3020506@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=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