From: Daniel Andersen <anddan@linux-user.net>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tejun Heo <tj@home-tj.org>,
netdev@oss.sgi.com
Subject: Re: via-velocity heads up (was (Re: Linux 2.6.9-rc4 - pls test (and no more patches))
Date: Mon, 11 Oct 2004 15:32:28 +0200 [thread overview]
Message-ID: <416A8B6C.30206@linux-user.net> (raw)
In-Reply-To: <20041011072307.GA18577@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> Linus Torvalds <torvalds@osdl.org> :
> [...]
>
>>Summary of changes from v2.6.9-rc3 to v2.6.9-rc4
>>============================================
>
> [...]
>
>>Fran?ois Romieu:
>> o via-velocity: properly manage the count of adapters
>> o via-velocity: removal of unused velocity_info.xmit_lock
>> o via-velocity: velocity_give_rx_desc() removal
>> o via-velocity: received ring wrong index and missing barriers
>> o via-velocity: early invocation of init_cam_filter()
>> o via-velocity: removal of incomplete endianness handling
>> o via-velocity: wrong buffer offset in velocity_init_td_ring()
>> o via-velocity: comment fixes
>
>
> The attribution is a bit misleading as Tejun Heo <tj@home-tj.org>
> did the real work (he appears in the logs though).
>
> People should really, really, test this code if they have been
> experiencing issues with the driver lately.
>
> Test reports welcome here or on netdev@oss.sgi.com.
>
I'm finally able to successfully use my On board VT6122 10/100/1000 Mb
PCI Ethernet Controller on my Abit KV8-Pro. I have not found any
problems with the via-velocity driver yet. Great work! :)
Daniel Andersen
--
next parent reply other threads:[~2004-10-11 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0410102016180.3897@ppc970.osdl.org>
[not found] ` <20041011072307.GA18577@electric-eye.fr.zoreil.com>
2004-10-11 13:32 ` Daniel Andersen [this message]
2004-10-11 16:53 ` via-velocity heads up (was (Re: Linux 2.6.9-rc4 - pls test (and no more patches)) Jerone Young
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=416A8B6C.30206@linux-user.net \
--to=anddan@linux-user.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.com \
--cc=tj@home-tj.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).