[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47B4CCBC.6050208@davidnewall.com>
Date: Fri, 15 Feb 2008 09:50:28 +1030
From: David Newall <davidn@...idnewall.com>
To: Arjan van de Ven <arjan@...ux.intel.com>
CC: 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
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.
--
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/
Powered by blists - more mailing lists