linux-kernel - Re: Feature Removals for 2.6.25

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <47B5068A.60808@keyaccess.nl>
Date:	Fri, 15 Feb 2008 04:27:06 +0100
From:	Rene Herman <rene.herman@...access.nl>
To:	David Newall <davidn@...idnewall.com>
CC:	Arjan van de Ven <arjan@...ux.intel.com>,
	Bill Davidsen <davidsen@....com>,
	Stephen Hemminger <shemminger@...ux-foundation.org>,
	Harvey Harrison <harvey.harrison@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	David Miller <davem@...emloft.net>,
	Jiri Slaby <jirislaby@...il.com>, Pavel Machek <pavel@...e.cz>,
	Christoph Hellwig <hch@....de>,
	Dominik Brodowski <linux@...do.de>, Andi Kleen <ak@...e.de>,
	Adrian Bunk <bunk@...sta.de>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Nick Piggin <npiggin@...e.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Len Brown <len.brown@...el.com>
Subject: Re: Feature Removals for 2.6.25

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/