On Mon, Nov 26, 2007 at 10:44:44PM -0500, Valdis.Kletnieks@vt.edu wrote: > I suspect that given the "once it escapes, it's cast in stone" view we take > towards user-visible API/etc, there isn't much *real* room for an > 'EXPERIMENTAL' flag anymore. Most of the usage should probably be confined to > individual drivers, where all we should need is a 'default n' and suitable > warning verbiage in the Kconfig file warning about the driver eating your > filesystems and small animals for breakfast. Potential corruptors are usually flagged with (DANGEROUS) in the text, (One may argue that they shouldn't have escaped -mm) > We certainly shouldn't have > one big flag for *all* in-progress drivers - I don't need to accidentally > enable a busticated ethernet driver because I want a USB widget. So no ethernet driver at all is better than a broken but mostly working one? Again if it isn't mostly working, it shouldn't have escaped -mm Dave -- http://www.codemonkey.org.uk -
| Ingo Molnar | [patch 12/13] syslets: x86: optimized copy_uatom() |
| Greg Kroah-Hartman | [PATCH 017/196] aoechr: Convert from class_device to device |
| Yinghai Lu | Re: 2.6.26, PAT and AMD family 6 |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Natalie Protasevich | [BUG] New Kernel Bugs |
