public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: James Corey <ploversegg@yahoo.com>,
	Stephen Hemminger <shemminger@linux-foundation.org>,
	Rob Sims <lkml-z@robsims.com>, Kyle Rose <krose@akamai.com>,
	linux-kernel@vger.kernel.org
Subject: Re: sk98lin for 2.6.23-rc1
Date: Sat, 8 Sep 2007 21:11:32 +0200	[thread overview]
Message-ID: <20070908191132.GD3563@stusta.de> (raw)
In-Reply-To: <46E2DF74.7040307@tmr.com>

On Sat, Sep 08, 2007 at 01:44:20PM -0400, Bill Davidsen wrote:
>...
> That was with 2.6.22.5 (or so), dropped back to an old kernel with sk98lin, 
> previously had uptimes in three digit days. Up for a week or so now.

There is a real long-term advantage of removing drivers like sk98lin 
because it forces people to report bugs if the new driver doesn't work  
instead of giving them the workaround of using the obsolete driver.    
And this has the (at first sight surprising) effect that removing code  
results in an improvement of the kernel.

> Haven't tried later kernels, don't intend to, while no network is really 
> secure, it not really useful.

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...

> Bill Davidsen

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-09-08 19:11 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 [this message]
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
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=20070908191132.GD3563@stusta.de \
    --to=bunk@kernel.org \
    --cc=davidsen@tmr.com \
    --cc=krose@akamai.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml-z@robsims.com \
    --cc=ploversegg@yahoo.com \
    --cc=shemminger@linux-foundation.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