Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269325AbTGXOtJ (ORCPT ); Thu, 24 Jul 2003 10:49:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270519AbTGXOtJ (ORCPT ); Thu, 24 Jul 2003 10:49:09 -0400 Received: from crosslink-village-512-1.bc.nu ([81.2.110.254]:29432 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S269325AbTGXOtH (ORCPT ); Thu, 24 Jul 2003 10:49:07 -0400 Subject: Re: time for some drivers to be removed? From: Alan Cox To: "Robert P. J. Day" Cc: Linux Kernel Mailing List In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1059058737.7994.25.camel@dhcp22.swansea.linux.org.uk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 24 Jul 2003 15:58:58 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 744 Lines: 15 On Iau, 2003-07-24 at 13:20, Robert P. J. Day wrote: > more to the point, there are drivers that seem to be perpetually > broken. as an example, the riscom8 driver has been borked for as > long as i can remember. at some point, shouldn't something like > this either be fixed or just removed? what's the point of > perpetually bundling a driver that doesn't even compile? So someone coming from 2.4 can fix it when they need it. You can tag such things with && OBSOLETE, we did that in 2.4. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/