public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: David Newall <davidn@davidnewall.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
	Bill Davidsen <davidsen@tmr.com>,
	Stephen Hemminger <shemminger@linux-foundation.org>,
	Harvey Harrison <harvey.harrison@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Miller <davem@davemloft.net>,
	Jiri Slaby <jirislaby@gmail.com>, Pavel Machek <pavel@suse.cz>,
	Christoph Hellwig <hch@lst.de>,
	Dominik Brodowski <linux@brodo.de>, Andi Kleen <ak@suse.de>,
	Adrian Bunk <bunk@stusta.de>, Greg Kroah-Hartman <gregkh@suse.de>,
	Nick Piggin <npiggin@suse.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Len Brown <len.brown@intel.com>
Subject: Re: Feature Removals for 2.6.25
Date: Fri, 15 Feb 2008 04:27:06 +0100	[thread overview]
Message-ID: <47B5068A.60808@keyaccess.nl> (raw)
In-Reply-To: <47B4CCBC.6050208@davidnewall.com>

On 15-02-08 00:20, David Newall wrote:

> Arjan van de Ven wrote:
>> Bill Davidsen wrote:
>>> Note that because the hardware is old, it's highly likely that most
>>> of it will be retired before that sk98lin driver needs a change. I
>>> can't see anyone using sk98lin on a new system, so it would be less
>>> contentious to let the hardware (or users) die of natural causes if
>>> you can.
>>>
>> the problem is that the new one DOES NOT GET FIXED.
>> THAT is a huge problem; it means we have a buggy driver...
> 
> If the old one works and the new one is buggy, it begs the question of
> why anybody bothered writing a new one in the first place.  "If it ain't
> broke, don't fix it," might have been good advice to follow.

Not generally. A usual scenario is the new driver working on newer hardware 
versions than the old one supports but not necessarily on all the old ones 
the previous driver supported if only due to to availability of the older 
hardware for testing.

Rene.

      reply	other threads:[~2008-02-15  3:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01  1:38 Feature Removals for 2.6.25 Harvey Harrison
2008-02-01  4:53 ` Arjan van de Ven
2008-02-01  5:18   ` Harvey Harrison
2008-02-01  6:33     ` Arjan van de Ven
2008-02-01  7:04       ` Harvey Harrison
2008-02-01  5:02 ` Feature Removals for 2.6.25 (USB driver api) Greg KH
2008-02-01  7:08 ` Feature Removals for 2.6.25 Stephen Hemminger
2008-02-02  1:29 ` Nick Piggin
2008-02-03 10:44 ` Feature Removals for 2.6.25 - old NCR53C9x driver Boaz Harrosh
2008-02-14  2:49 ` Feature Removals for 2.6.25 Bill Davidsen
2008-02-14  2:55   ` Stephen Hemminger
2008-02-14 18:16     ` Bill Davidsen
2008-02-14 18:24       ` Arjan van de Ven
2008-02-14 18:26         ` Christoph Hellwig
2008-02-14 23:20         ` David Newall
2008-02-15  3:27           ` Rene Herman [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=47B5068A.60808@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=bunk@stusta.de \
    --cc=davem@davemloft.net \
    --cc=davidn@davidnewall.com \
    --cc=davidsen@tmr.com \
    --cc=gregkh@suse.de \
    --cc=harvey.harrison@gmail.com \
    --cc=hch@lst.de \
    --cc=jirislaby@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@brodo.de \
    --cc=npiggin@suse.de \
    --cc=pavel@suse.cz \
    --cc=randy.dunlap@oracle.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