From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Kyle Rose <krose@krose.org>, Bill Davidsen <davidsen@tmr.com>,
James Corey <ploversegg@yahoo.com>, Rob Sims <lkml-z@robsims.com>,
linux-kernel@vger.kernel.org
Subject: Re: sk98lin for 2.6.23-rc1
Date: Tue, 11 Sep 2007 10:05:26 +0200 [thread overview]
Message-ID: <20070911100526.6aa5d463@oldman> (raw)
In-Reply-To: <20070909111326.GF3563@stusta.de>
On Sun, 9 Sep 2007 13:13:26 +0200
Adrian Bunk <bunk@kernel.org> wrote:
> On Sat, Sep 08, 2007 at 10:42:20PM -0400, Kyle Rose wrote:
> >
> > > You are a regular reader of linux-kernel, and therefore the sk98lin
> > > removal can hardly be a surprise for you. If you prefer whining over
> > > helping to improve the kernel that's your choice...
> > >
> > In my case the issue is simply one of practicality: I cannot go to the
> > data center 5 times per day to reboot my colo box. Therefore, I run
> > sk98lin. It's really that simple.
>
> When did you report this bug the first time?
>
> What we need is that people when testing a new kernel they plan to use
> test the new drivers *and report the bugs if they run into any*.
>
> What could we have done so that you reported your bug without removing
> the sk98lin driver?
>
> > Kyle
>
> cu
> Adrian
There are several different problems in this thread:
1. The removal of old sk98lin driver caused some users to be forced to use
skge. These users have uncovered issues with the dual port fiber based versions
of the board.
Short term: The sk98lin driver should be restored to previous state,
and the PCI table should be used to limit the usage to only fiber systems.
If Adrian doesn't do it, I'll do it when I return from Germany.
Long term: I have fiber based board (thanks ebay) on the way to resolve
skge bug.
2. Sky2 driver has it's own fiber based problems. Solve these after skge fiber.
3. Sky2 doesn't have as many workarounds for hardware problems as vendor sk98lin
driver.
next prev parent reply other threads:[~2007-09-11 8:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 15:16 sk98lin for 2.6.23-rc1 Kyle Rose
2007-07-26 16:28 ` Jan Engelhardt
2007-07-26 16:30 ` Kyle Rose
2007-07-26 16:41 ` Jan Engelhardt
2007-07-27 1:07 ` Kyle Rose
2007-07-26 16:57 ` Adrian Bunk
2007-07-26 22:58 ` Chris Stromsoe
2007-07-26 23:38 ` Bill Davidsen
2007-07-26 23:41 ` Jeff Garzik
2007-07-30 3:01 ` Rob Sims
2007-09-05 9:22 ` Stephen Hemminger
2007-09-05 19:42 ` James Corey
2007-09-05 21:04 ` Kyle Rose
2007-09-05 23:00 ` Stephen Hemminger
2007-09-08 17:44 ` Bill Davidsen
2007-09-08 19:11 ` Adrian Bunk
2007-09-09 2:42 ` Kyle Rose
2007-09-09 4:48 ` Willy Tarreau
2007-09-09 11:13 ` Adrian Bunk
2007-09-11 8:05 ` Stephen Hemminger [this message]
2007-09-11 11:54 ` Adrian Bunk
2007-09-11 14:29 ` Bill Davidsen
2007-09-11 15:03 ` Adrian Bunk
2007-09-11 22:37 ` Willy Tarreau
2007-09-11 22:20 ` James Corey
2007-09-09 12:54 ` Chris Stromsoe
2007-11-06 22:23 ` Stephen Hemminger
2007-11-07 1:42 ` Chris Stromsoe
2007-09-10 14:32 ` Bill Davidsen
2007-09-10 15:39 ` Adrian Bunk
2007-09-11 4:23 ` Kyle Moffett
2007-09-12 16:46 ` Torsten Kaiser
2007-07-26 19:17 ` Stephen Hemminger
2007-07-26 23:52 ` Bill Davidsen
2007-07-27 1:13 ` Kyle Rose
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=20070911100526.6aa5d463@oldman \
--to=shemminger@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=davidsen@tmr.com \
--cc=krose@krose.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml-z@robsims.com \
--cc=ploversegg@yahoo.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