From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Stephane Casset <sept@logidee.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] via-rhine for 2.5.5
Date: Thu, 21 Feb 2002 05:18:24 -0500 [thread overview]
Message-ID: <3C74C970.5AAE6A68@mandrakesoft.com> (raw)
In-Reply-To: <20020221095905.GA19625@logidee.com>
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
Stephane Casset wrote:
> --- drivers/net/via-rhine.c.orig Thu Feb 21 10:49:54 2002
> +++ drivers/net/via-rhine.c Thu Feb 21 10:55:39 2002
> @@ -1754,7 +1754,7 @@
> - remove: via_rhine_remove_one,
> + remove: __devexit_p(via_rhine_remove_one),
this is ok
> -static void __exit via_rhine_cleanup (void)
> +static void __devexit via_rhine_cleanup (void)
this is definitely wrong
I'm also surprised you managed to compile via-rhine without the attached
patch, which is needed to fix the build.
Jeff
--
Jeff Garzik | "Why is it that attractive girls like you
Building 1024 | always seem to have a boyfriend?"
MandrakeSoft | "Because I'm a nympho that owns a brewery?"
| - BBC TV show "Coupling"
[-- Attachment #2: via-rhine-2.5.5.patch --]
[-- Type: text/plain, Size: 553 bytes --]
diff -Nru a/drivers/net/via-rhine.c b/drivers/net/via-rhine.c
--- a/drivers/net/via-rhine.c Thu Feb 21 05:17:43 2002
+++ b/drivers/net/via-rhine.c Thu Feb 21 05:17:43 2002
@@ -321,6 +321,7 @@
VT86C100A = 0,
VT6102,
VT3043,
+ VT6105,
};
struct via_rhine_chip_info {
@@ -349,7 +350,7 @@
{ "VIA VT6102 Rhine-II", RHINE_IOTYPE, 256,
CanHaveMII | HasWOL },
{ "VIA VT3043 Rhine", RHINE_IOTYPE, 128,
- CanHaveMII | ReqTxAlign }
+ CanHaveMII | ReqTxAlign },
{ "VIA VT6105 Rhine-III", RHINE_IOTYPE, 256,
CanHaveMII | HasWOL },
};
prev parent reply other threads:[~2002-02-21 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 9:59 [PATCH] via-rhine for 2.5.5 Stephane Casset
2002-02-21 10:18 ` 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=3C74C970.5AAE6A68@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sept@logidee.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