Re: RFC: deprecate CONFIG_X86_CPU_DEBUG and schedule it for rapidremoval
From: H. Peter Anvin
Date: Fri Jan 22 2010 - 20:07:11 EST
On 01/22/2010 04:53 PM, Andrew Morton wrote:
> Would it not be better to fix that problem (perhaps just with the
> revert) so that 2.6.33, 2.6.32.x and earlier can be fixed? Then we can
> nuke the feature in 2.6.34.
> Alternatively, we can nuke the feature from 2.6.33 and 2.6.32.x and
> earlier right now. Where "nuke" might mean "make it difficult to
> Whatever. Bottom line is that it'd be nice to do something to fix up
> 2.6.33 and earlier.
I would be all for nuking the feature immediately. The easiest way to
nuke the feature quickly is to make it a noninteractive Kconfig feature.
All in favor?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/