From: Srihari Vijayaraghavan <harisri@bigpond.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@oss.sgi.com, Srihari Vijayaraghavan <harisri@telstra.com>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [patch 0/3] 2.6.5-netdev2 - r8169 update
Date: Wed, 14 Apr 2004 09:42:12 +1000 [thread overview]
Message-ID: <200404140942.12659.harisri@bigpond.com> (raw)
In-Reply-To: <20040407231332.A25021@electric-eye.fr.zoreil.com>
Hello Francois,
On Thursday 08 April 2004 07:13, Francois Romieu wrote:
> The following serie of patches applies against 2.6.5 + 2.6.5-netdev2.
>
> - r8169-missing-static.patch
> missing 'static' qualifiers.
>
> - r8169-irq-handler-status.patch
> fix status code bogosity for the irq handler if the r8169 interrupt is
> shared.
>
> - r8169-mod_timer.patch
> missing "jiffies +" in mod_timer(). The link recovery code seems to work
> again.
>
> An update of the patch against 2.6.5 for the whole driver is available for
> testers at:
> http://www.fr.zoreil.com/people/francois/misc/20040407-2.6.5-r8169.c-stable
>.patch
I have tested this under moderate network load on my Athlon 64 (2.6.5 64 bit
kernel). It is working fine.
Thanks
Hari
prev parent reply other threads:[~2004-04-13 23:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 21:55 [patch 0/7] 2.6.5-bk-netdev - r8169 queue Francois Romieu
2004-04-05 21:56 ` [patch 1/7] " Francois Romieu
2004-04-05 21:57 ` [patch 2/7] " Francois Romieu
2004-04-05 21:58 ` [patch 3/7] " Francois Romieu
2004-04-05 21:58 ` [patch 4/7] " Francois Romieu
2004-04-05 21:59 ` [patch 5/7] " Francois Romieu
2004-04-05 21:59 ` [patch 6/7] " Francois Romieu
2004-04-05 22:00 ` [patch 7/7] " Francois Romieu
2004-04-07 21:13 ` [patch 0/3] 2.6.5-netdev2 - r8169 update Francois Romieu
2004-04-07 21:14 ` [patch 1/3] " Francois Romieu
2004-04-07 21:15 ` [patch 2/3] " Francois Romieu
2004-04-07 21:16 ` [patch 3/3] " Francois Romieu
2004-04-13 18:27 ` [patch 1/3] " Jeff Garzik
2004-04-13 23:42 ` Srihari Vijayaraghavan [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=200404140942.12659.harisri@bigpond.com \
--to=harisri@bigpond.com \
--cc=harisri@telstra.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.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;
as well as URLs for NNTP newsgroup(s).