Message-ID: <3F1FFC94.7080409@basmevissen.nl>
Date: Thu, 24 Jul 2003 17:34:44 +0200
From: Bas Mevissen <ml@basmevissen.nl>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: time for some drivers to be removed?
References: <Pine.LNX.4.53.0307240817520.19533@localhost.localdomain> <1059058737.7994.25.camel@dhcp22.swansea.linux.org.uk>
In-Reply-To: <1059058737.7994.25.camel@dhcp22.swansea.linux.org.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1081
Lines: 31

Alan Cox wrote:

> 
> 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.
> 

Is this something for the kernel config? Just below CONFIG_EXPERIMENTEL 
in the menu, add CONFIG_OBSOLETE. The 'make allyesconfig' and the like 
can ignore experimental and obsolete stuff.

This would make a reasonable Q-requirement for 2.6.0 that at least the 
kernel compiles with 'make allyesconfig'. The only thing open is to 
decide what is obsolete and what not (and needs fix). That is not 
trivial. IMHO, Linus some time ago had a good statement about it, but it 
is somewhat hard to see how long something is broken from the code alone :-)

If this is a good idea, I'll supply a patch for 2.6.0-something with at 
least some non-compiling stuff marked obsolete.

Regards,

Bas.


-
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/