From: Jeff Garzik <jgarzik@pobox.com>
To: maxer <maxer@xmission.com>
Cc: linux-kernel@vger.kernel.org, Netdev <netdev@oss.sgi.com>
Subject: Re: SysKonnect sk98lin Gigabit lan missing in action from 2.6.10 on
Date: Fri, 04 Feb 2005 16:07:10 -0500 [thread overview]
Message-ID: <4203E3FE.2090806@pobox.com> (raw)
In-Reply-To: <42038994.20401@xmission.com>
maxer wrote:
> What is the status of sk98lin? Do we have to wait until Syskonnect gets
> their act together
> and write a new driver for 2.6.10?
>
> Their latest is Oct 2004 and not at all compatible with 2.6.10 and beyond.
I've been telling SysKonnect for _years_ that they need to split up
their patches, but they still keep sending ever-larger jumbo driver
update patches.
Stephen Hemminger split up their patch into a bunch of patches, and I
applied several of those.
Apparently, Stephen also got sick of trying to patch and clean sk98lin,
so he went and wrote his own "skge" driver. It's available in my
netdev-2.6 queue, and should be in the latest -mm.
Jeff
next parent reply other threads:[~2005-02-04 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42038994.20401@xmission.com>
2005-02-04 21:07 ` Jeff Garzik [this message]
2005-02-04 22:28 ` SysKonnect sk98lin Gigabit lan missing in action from 2.6.10 on Lawrence Walton
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=4203E3FE.2090806@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxer@xmission.com \
--cc=netdev@oss.sgi.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).