Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263319AbTGXMHK (ORCPT ); Thu, 24 Jul 2003 08:07:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263355AbTGXMHK (ORCPT ); Thu, 24 Jul 2003 08:07:10 -0400 Received: from tomts10.bellnexxia.net ([209.226.175.54]:39578 "EHLO tomts10-srv.bellnexxia.net") by vger.kernel.org with ESMTP id S263319AbTGXMHJ (ORCPT ); Thu, 24 Jul 2003 08:07:09 -0400 Date: Thu, 24 Jul 2003 08:20:44 -0400 (EDT) From: "Robert P. J. Day" X-X-Sender: rpjday@localhost.localdomain To: Linux kernel mailing list Subject: time for some drivers to be removed? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 819 Lines: 18 i've mentioned this before, but in a perfect world, should it be possible to build a release version of the kernel with "make allyesconfig". this is generally not possible, since there's always the occasional broken driver that just won't compile. 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? rday - 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/